CVE-2018-25197
8.2PlayJoom · PlayJoom
PlayJoom version 0.10.1 is vulnerable to an unauthenticated SQL injection flaw in the catid parameter, allowing attackers to execute arbitrary database queries and extract sensitive information.
Executive summary
A critical SQL injection vulnerability in PlayJoom 0.10.1 allows unauthenticated attackers to exfiltrate sensitive database information, posing a significant risk to data confidentiality.
Vulnerability
This is a classic SQL injection (CWE-89) vulnerability located within the catid parameter of the index.php script. Unauthenticated attackers can leverage this flaw to inject malicious SQL commands, enabling them to bypass security controls and access backend database contents.
Business impact
Successful exploitation of this vulnerability allows unauthorized access to the underlying database, which may contain user credentials, configuration data, and proprietary application information. Given the CVSS score of 8.2, this represents a high-severity risk that could lead to full database compromise, potential identity theft, and severe reputational damage.
Remediation
Immediate Action: There is currently no official patch available for this vulnerability. Administrators should immediately restrict access to the affected application or disable the PlayJoom component if it is not business-critical.
Proactive Monitoring: Security teams should monitor web server logs for anomalous GET requests containing SQL syntax, particularly involving the catid parameter. Additionally, monitor database query logs for unusual or unauthorized execution patterns.
Compensating Controls: Deploy a Web Application Firewall (WAF) with rules configured to detect and block SQL injection patterns in incoming HTTP requests to protect the application until a permanent fix is implemented.
Exploitation status
Public Exploit Available: Yes, a proof-of-concept exploit is publicly documented in the Exploit Database (EDB-ID: 45803).
Analyst recommendation
Due to the high severity of this SQL injection vulnerability and the availability of a public proof-of-concept, immediate action is required to secure the environment. If a vendor update is not provided, the application should be considered insecure and isolated from the network to prevent unauthorized data exfiltration. Prioritize the implementation of WAF rules and rigorous log monitoring to detect any attempts to leverage this publicly known attack vector.
Sources
Originally found and disclosed by Ihsan Sencan, per the CVE Program record.
- ExploitDB-45803 Exploit / PoC
- VulnCheck Advisory: PlayJoom 0.10.1 SQL Injection via catid Parameter Third-party advisory