CVE-2019-25573

7.1

GreenCMS · Green CMS

Green CMS 2.0 contains an SQL injection vulnerability in the cat parameter, allowing authenticated attackers to execute arbitrary SQL queries.

Executive summary

An authenticated SQL injection vulnerability in Green CMS 2.0 allows attackers to manipulate database queries and extract sensitive information from the underlying database.

Vulnerability

This vulnerability is an SQL injection (CWE-89) located in the cat parameter of the index.php file. The flaw is reachable by authenticated attackers who can send specifically crafted GET requests to the admin post index endpoint to execute arbitrary SQL commands.

Business impact

Successful exploitation of this vulnerability allows an authenticated attacker to perform unauthorized database operations, which may lead to the exfiltration of sensitive application data or the corruption of database records. With a CVSS score of 7.1, this represents a high-severity risk to the confidentiality and integrity of the application, potentially resulting in unauthorized access to administrative functions or backend systems.

Remediation

Immediate Action: As no official patch is currently available, administrators should restrict access to administrative interfaces to trusted users only and implement strict input validation for all parameters.

Proactive Monitoring: Security teams should monitor web access logs for suspicious GET requests containing SQL syntax, such as "BENCHMARK" or other SQL keywords, directed at the index.php file.

Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block common SQL injection patterns, particularly those targeting the cat parameter in the administrative URL path.

Exploitation status

Public Exploit Available: Yes — an exploit script is available via Exploit-DB (EDB-ID 46244).

Analyst recommendation

Given the availability of public exploit code and the potential for significant data compromise, organizations currently utilizing Green CMS 2.0 should prioritize migrating to a secure alternative or isolating the instance from internal networks. If migration is not immediately feasible, ensure the application is placed behind a robust WAF and that strict access controls are enforced to minimize the attack surface.

Sources

Originally found and disclosed by Ihsan Sencan, per the CVE Program record.