CVE-2023-53975

8.2

TheDigiCraft · Atom CMS

Atom CMS 2.0 is vulnerable to unauthenticated SQL injection, allowing remote attackers to manipulate database queries via the 'id' parameter on the administrative index page.

Executive summary

A critical, unauthenticated SQL injection vulnerability in Atom CMS 2.0 allows remote attackers to compromise the database and potentially gain full control of the application.

Vulnerability

This is an improper neutralization of special elements used in an SQL command (CWE-89) located within the administrative index page. The flaw allows an unauthenticated attacker to inject malicious SQL code through the 'id' parameter to execute time-based blind SQL injection attacks.

Business impact

Successful exploitation of this vulnerability permits unauthorized access to the underlying database, which may result in the exfiltration of sensitive user data, modification of application content, or administrative account takeover. Given the CVSS score of 8.2, this flaw poses a high risk to business operations, potentially leading to significant data breaches and total loss of system integrity.

Remediation

Immediate Action: As no official patch is available, administrators should restrict access to the administrative directory via network-level controls or web server authentication.

Proactive Monitoring: Security teams should review web server access logs for anomalous POST requests to the admin index page containing SQL syntax, such as sleep commands or union statements.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block SQL injection patterns to provide a virtual patch until the software is updated or replaced.

Exploitation status

Public Exploit Available: Yes, a functional exploit is available via the Exploit Database (EDB-ID: 51086).

Analyst recommendation

Due to the severity of this unauthenticated SQL injection, immediate action is required to secure the environment. If the software cannot be patched or adequately protected by a WAF, it should be removed from public-facing infrastructure to prevent unauthorized database access.

Sources

Originally found and disclosed by Hubert Wojciechowski, per the CVE Program record.