CVE-2017-20271 in StreetGuessr Game
Summary
by MITRE • 06/19/2026
Joomla StreetGuessr Game 1.1.8 contains an SQL injection vulnerability that allows unauthenticated attackers to execute arbitrary SQL queries by injecting malicious code through the catid parameter. Attackers can send GET requests to index.php with the option=com_streetguess&view=maps parameters and inject SQL code in the catid parameter to extract sensitive database information including version and database names.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Analysis
by VulDB Data Team • 07/01/2026
The Joomla StreetGuessr Game component version 1.1.8 contains a critical sql injection vulnerability that represents a significant threat to web application security. This vulnerability resides within the handling of user input parameters and specifically targets the catid parameter in the url structure. The flaw allows unauthenticated attackers to execute arbitrary sql commands without requiring any valid credentials or session tokens, making it particularly dangerous as it can be exploited by anyone who can access the vulnerable application. The attack vector is straightforward and utilizes standard http get requests directed at the index.php endpoint with specific parameters including option=com_streetguess and view=maps.
The technical implementation of this vulnerability stems from inadequate input validation and sanitization within the application's data processing pipeline. When the catid parameter is processed, it fails to properly escape or sanitize user-supplied input before being incorporated into sql queries executed against the underlying database system. This lack of proper input filtering creates a direct path for malicious sql code injection that bypasses normal security controls and authentication mechanisms. The vulnerability affects the core database interaction logic where user-provided category identifiers are directly concatenated into sql statements without appropriate parameterization or escaping techniques.
The operational impact of this vulnerability extends beyond simple data extraction and represents a comprehensive threat to database confidentiality and system integrity. Attackers can leverage this weakness to extract sensitive information including database version numbers, table structures, and potentially user credentials or other confidential data stored within the application's database. The ability to execute arbitrary sql commands means that attackers could not only read data but also modify or delete database records, potentially leading to complete system compromise or data loss. This vulnerability undermines the fundamental security assumptions of the web application and creates opportunities for further exploitation or lateral movement within the network infrastructure.
Security professionals should recognize this vulnerability as a classic example of cwe-89 sql injection weakness that aligns with multiple tactics described in the mitre att&ck framework under initial access and credential access phases. The unauthenticated nature of the exploit means that defenders must treat this as an immediate priority for remediation since no authentication is required to exploit the flaw. Organizations should implement immediate mitigations including input validation, parameterized queries, and web application firewalls to protect against this specific attack vector while also conducting comprehensive vulnerability assessments to identify similar weaknesses in other components or applications within their infrastructure.
Mitigation strategies should include immediate patching of the affected Joomla component to version 1.1.9 or higher where the sql injection vulnerability has been addressed through proper input validation and parameterization of database queries. Additionally, administrators should implement proper input sanitization measures that filter or escape special characters in user-provided parameters before they are processed by the application. Network-level protections such as web application firewalls and intrusion detection systems can provide additional defense-in-depth layers to detect and block malicious sql injection attempts. Regular security auditing and penetration testing should be conducted to identify similar vulnerabilities across the entire application portfolio, ensuring that all components follow secure coding practices and maintain appropriate input validation controls to prevent sql injection attacks of this nature.