Quick answers
- Is CVE-2026-108900 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-108900 being exploited in the wild.
- How severe is CVE-2026-108900?
- High severity, with a CVSS score of 7.3, published 12 October 2026.
- Which products and versions are affected?
- Exponent CMS CMS up to 3.0.2patch2.
- Is there a fix for CVE-2026-108900?
- No fixed version is recorded yet. Disable XML-RPC by setting USE_XMLRPC to '0' in config.php unless it is explicitly required for your deployment. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-108900 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-108900?
- Check whether you run Exponent CMS CMS at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
Disable XML-RPC by setting USE_XMLRPC to '0' in config.php unless it is explicitly required for your deployment.
Technical details
An unauthenticated SQL injection exists in the userLogin() function of xmlrpc.php when the USE_XMLRPC feature is enabled. The vulnerability occurs because user-supplied username values from XML-RPC methods (metaWeblog.getUsersBlogs, blogger.getUsersBlogs) are concatenated directly into SQL WHERE clauses without parameterization or escaping, unlike the protected web login controller. An attacker can exploit this before password verification by crafting a malicious username to alter the query logic.
Affected products
- Exponent CMS CMS up to 3.0.2patch2
Timeline
- 2026-10-12: disclosed
- other: Exploit publicly disclosed; vendor did not respond to early disclosure notification