Vulnerability record · CVE-2018-6605 · published 5 February 2018
CVE-2018-6605: Joomla Zh BaiduMap component SQL injection via id parameter
ZZh Baidumap Project · Zh Baidumap
The Zh BaiduMap 3.0.0.1 component for Joomla! is vulnerable to SQL injection through the id parameter in getPlacemarkDetails, getPlacemarkHoverText, getPathHoverText, and getPathDetails requests. Because the flaw is unauthenticated and remotely reachable, it exposes the site's database to direct manipulation. The record does not list affected Joomla! versions beyond the component version.
Description
SQL Injection exists in the Zh BaiduMap 3.0.0.1 component for Joomla! via the id parameter in a getPlacemarkDetails, getPlacemarkHoverText, getPathHoverText, or getPathDetails request.
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Automated analysis
critical priorityUnauthenticated remote SQL injection with a public exploit and very high EPSS probability warrants immediate remediation.
What it is
The Zh BaiduMap 3.0.0.1 component for Joomla! is vulnerable to SQL injection through the id parameter in getPlacemarkDetails, getPlacemarkHoverText, getPathHoverText, and getPathDetails requests. Because the flaw is unauthenticated and remotely reachable, it exposes the site's database to direct manipulation. The record does not list affected Joomla! versions beyond the component version.
Impact
An attacker can read, modify, or delete data in the underlying database, including Joomla! user credentials and configuration. Full compromise of the CMS and potentially the hosting account follows from that access.
Attack surface
Reached over the network via HTTP requests to the component's endpoints with a crafted id parameter. No authentication or user interaction is required per the CVSS vector (AV:N/AC:L/PR:N/UI:N).
Exploitation
A public Exploit-DB entry (43974) exists, and EPSS estimates a 57.7% probability of exploitation in 30 days (99th percentile). The CVE is not listed in CISA KEV.
What to do
- Update or remove the Zh BaiduMap component; if no fixed version exists, uninstall it.
- Apply a WAF rule blocking SQL metacharacters in the id parameter on the affected endpoints.
- Restrict access to the component's request handlers where possible.
- Audit the Joomla! database for unauthorized changes and rotate credentials if compromise is suspected.
Detection
- Monitor web logs for requests to getPlacemarkDetails, getPlacemarkHoverText, getPathHoverText, or getPathDetails with suspicious id values.
- Alert on SQL syntax patterns (UNION, SELECT, quotes, comment markers) in the id parameter.
- Review database error logs for injection-related failures from the component.
This assessment is produced automatically and is not human-reviewed. Verify against the vendor advisory before acting on it.
Affected products
1 vulnerable configurations from NVD's CPE data, grouped by vendor and product.
References
| Link | Tags |
|---|---|
| https://www.exploit-db.com/exploits/43974/ | ExploitThird Party AdvisoryVDB Entry |
| https://www.exploit-db.com/exploits/43974/ | ExploitThird Party AdvisoryVDB Entry |
Track CVE-2018-6605 inside VULONE
Watch it alongside the ransomware crews, C2 infrastructure and forum chatter that reference it, query it through the API and pull it into your SIEM over TAXII.
Related vulnerabilities
Same products first, then exploited flaws of the same weakness class.
Source: NIST National Vulnerability Database (record CVE-2018-6605), CISA KEV, FIRST EPSS (scores of 2026-09-26). This page is refreshed as NVD updates the record.
