WP Go Maps (formerly WP Google Maps) <= 7.11.17 - SQL Injection
Strategic Overview
- Status
- Patched in 7.11.18
- Affected Plugin
- WP Go Maps – Google Map, OpenStreetMap, Leaflet Map
- Affected Version
<= 7.11.17- CVSS
- 9.8Critical
- Weakness type
- CWE-89 · Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
- CVE
CVE-2019-10692
At a glance
CVE-2019-10692 is a critical-severity Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in the WP Go Maps WordPress plugin, affecting versions <= 7.11.17. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 7.11.18; sites on affected versions should update now. Disclosed September 2020.
Vulnerability Overview
In the wp-google-maps plugin before 7.11.18 for WordPress, includes/class.rest-api.php in the REST API does not sanitize field names before a SELECT statement.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-89: Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')
Reaching this weakness in WP Go Maps <= 7.11.17 takes a caller who can reach the endpoint. SQL injection happens when request data is concatenated into a query instead of being bound as a parameter, letting an attacker change the structure of the statement rather than just its values.
A working injection can read any table the database user can see, which on a WordPress install means user records, password hashes and session or API secrets stored in options. For WP Go Maps the fix is 7.11.18: builds <= 7.11.17 are affected, anything from 7.11.18 onward is not.
Remediation
Update to version 7.11.18, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WP Go Maps: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Go Maps 7.11.18 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Other vulnerabilities in WP Go Maps – Google Map, OpenStreetMap, Leaflet Map
- 7.5CVE-2026-84780: WP Go Maps DoS
CVE-2026-84780 - 7.2CVE-2025-11307: Google Maps <= 9.0.47 Stored Cross-Site Scripting
CVE-2025-11307 - 6.4CVE-2026-4268: WP Go Maps Authenticated (Subscriber+) Stored XSS
CVE-2026-4268 - 6.4CVE-2024-5994: WP Go Maps (formerly WP Google Maps) Stored XSS
CVE-2024-5994 - 6.4CVE-2024-3557: WP Go Maps (formerly WP Google Maps) Stored XSS
CVE-2024-3557 - 6.4CVE-2024-1582: WP Go Maps (formerly WP Google Maps) Stored XSS
CVE-2024-1582 - 6.4WP Google Maps <= 6.3.14 Stored Cross-Site Scripting
- 6.1CVE-2024-29931: WP Google Maps <= 9.0.29 Reflected XSS
CVE-2024-29931
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C