Skip to content
CVE-2026-108900: SQL Injection Vulnerability in Exponent CMS

CVE-2026-108900: SQL Injection Vulnerability in Exponent CMS

First seen 13 Oct 2026, 11:30 UTC • •

Article Content

Browse articles
ThreatCluster AI
ThreatCluster •October 13, 2026 at 13:30 UTC
  • •CVE-2026-108900 affects Exponent CMS versions up to 3.0.2patch2.
  • •The vulnerability allows unauthenticated remote SQL injection via xmlrpc.php.
  • •Public exploit code increases the risk of opportunistic attacks on exposed systems.

A SQL injection vulnerability (CVE-2026-108900) has been identified in Exponent CMS versions up to 3.0.2patch2, specifically affecting the userLogin function in xmlrpc.php. This vulnerability allows unauthenticated remote attackers to manipulate SQL queries, potentially exposing or altering sensitive information in the CMS database. The exploit has been publicly disclosed, raising the risk of opportunistic attacks, particularly against internet-facing instances with XML-RPC enabled. The vendor was contacted prior to the disclosure but did not respond. Mitigation recommendations include disabling XML-RPC if not needed and applying SQL-injection filtering as a temporary measure. The vulnerability has a CVSS score of 6.9, indicating a medium severity level. Affected systems should monitor logs for unusual activity and limit database account privileges.

Start a free Starter trial for enhanced analysis

Ask AI about this cluster

Updated just now How this analysis works

Timeline

2026-10-12
CVE-2026-108900 published
A SQL injection vulnerability in Exponent CMS was publicly disclosed with a CVSS score of 6.9.
Redpacketsecurity

More articles in this cluster (4)

Following this threat?

Track CVE-2026-108900 in your own feed — you're alerted when they show up in new reporting, leak sites or exploitation.

Free account · no card needed

Common questions

Which versions of Exponent CMS are affected?
Exponent CMS versions up to 3.0.2patch2 are affected by this vulnerability.
Is there a patch available for this vulnerability?
No fixed release has been established yet, and the vendor has not responded to inquiries.
What immediate actions should be taken?
Disable XML-RPC if not needed, apply SQL-injection filtering, and monitor logs for unusual activity.