CVE-2019-10692

CRITICALNVD 9.89.8—
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2022-05-04. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Weaponized
9.8EG
EchelonGraph verdictMitigate this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 79%
  • Public exploit code is available (Metasploit, epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 79%CVSS: 9.8Exploit: Metasploit · epss top5pct · epss high · public exploitExposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

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.

CVSS v3
9.8
EG Score
9.8CRITICALmedium confidence
EG Risk
80
EG Risk 80/100CISA SSVC

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation79% × 40%
Automatability30% × 15%
CISA SSVC: Track at low, Track* at medium and Attend at high mission impact.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
79%
EPSS %ILE
99th
KEV
Not listed

CISA SSVCTrack at low, Track* at medium and Attend at high mission impact.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low or medium mission impact and sooner than that at high; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation public PoC (EG-KEV: weaponized) · Automatable unknown (not published for this CVE) · Technical impact total (CVSS ≥ 9.0). Mission impact is CISA's Mission & Well-being decision point, and only you can judge it: high means the affected system is essential to your organisation's mission, or its compromise could cause irreversible harm to people. CISA's decision table

Published

April 2, 2019

Last Modified

November 21, 2024

Advisory Details (3)

Auto-updated Oct 5, 2026
Fix referenced — no release confirmed yet.
generic

WP Go Maps – Google Map, OpenStreetMap, Leaflet Map – WordPress plugin | WordPress.org

https://wordpress.org/plugins/wp-google-maps/#developers
generic

WordPress Google Maps Plugin SQL Injection | Metasploit Module

http://www.rapid7.com/db/modules/auxiliary/admin/http/wp_google_maps_sqli
generic

Packet Storm

http://packetstormsecurity.com/files/159640/WordPress-Rest-Google-Maps-SQL-Injection.html

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 3× in last 7d / 13× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-10-04 23:18 UTCEPSS rescore
  2. 2026-09-30 14:59 UTCEPSS rescore
  3. 2026-09-30 10:08 UTCEG score recompute
  4. 2026-09-26 15:53 UTCEPSS rescore
  5. 2026-09-24 13:59 UTCEPSS rescore
  6. 2026-09-23 13:43 UTCEPSS rescore
  7. 2026-09-21 20:27 UTCEPSS rescore
  8. 2026-09-18 19:22 UTCEPSS rescore
  9. 2026-09-16 14:04 UTCEPSS rescore
  10. 2026-09-13 16:42 UTCEPSS rescore
  11. 2026-09-12 14:56 UTCEPSS rescore
  12. 2026-09-08 21:55 UTCEPSS rescore
  13. 2026-09-06 13:44 UTCEPSS rescore
  14. 2026-09-05 15:24 UTCEPSS rescore
  15. 2026-09-04 05:02 UTCEPSS rescore
  16. 2026-08-30 19:13 UTCEPSS rescore
  17. 2026-08-28 21:36 UTCEPSS rescore
  18. 2026-08-25 13:45 UTCEPSS rescore
  19. 2026-08-20 22:51 UTCEPSS rescore
  20. 2026-08-19 17:00 UTCEPSS rescore
  21. 2026-08-16 14:52 UTCEPSS rescore
  22. 2026-08-16 02:10 UTCEPSS rescore
  23. 2026-08-15 01:26 UTCEPSS rescore
  24. 2026-08-12 13:47 UTCEPSS rescore
  25. 2026-08-04 15:05 UTCEPSS rescore
Show 48 more
  1. 2026-07-30 16:24 UTCEPSS rescore
  2. 2026-07-30 01:27 UTCEPSS rescore
  3. 2026-07-26 14:51 UTCEPSS rescore
  4. 2026-07-24 14:14 UTCEPSS rescore
  5. 2026-07-24 14:14 UTCEPSS rescore
  6. 2026-07-23 14:15 UTCEPSS rescore
  7. 2026-07-23 01:38 UTCEG score recompute
  8. 2026-07-22 22:18 UTCEG score recompute
  9. 2026-07-22 14:05 UTCEPSS rescore
  10. 2026-07-21 15:22 UTCEPSS rescore
  11. 2026-07-21 15:22 UTCEPSS rescore
  12. 2026-07-19 02:26 UTCEPSS rescore
  13. 2026-07-19 02:26 UTCEPSS rescore
  14. 2026-07-15 16:55 UTCEPSS rescore
  15. 2026-07-13 22:27 UTCEPSS rescore
  16. 2026-07-11 08:24 UTCEPSS rescore
  17. 2026-07-08 15:11 UTCEPSS rescore
  18. 2026-07-05 02:27 UTCEPSS rescore
  19. 2026-07-01 15:03 UTCEPSS rescore
  20. 2026-07-01 15:03 UTCEPSS rescore
  21. 2026-06-28 04:54 UTCEPSS rescore
  22. 2026-06-28 04:53 UTCEPSS rescore
  23. 2026-06-25 13:47 UTCEPSS rescore
  24. 2026-06-25 13:47 UTCEPSS rescore
  25. 2026-06-24 14:03 UTCEPSS rescore
  26. 2026-06-24 14:02 UTCEPSS rescore
  27. 2026-06-23 21:30 UTCEPSS rescore
  28. 2026-06-23 21:30 UTCEPSS rescore
  29. 2026-06-19 19:23 UTCEPSS rescore
  30. 2026-06-19 19:23 UTCEPSS rescore
  31. 2026-06-16 17:50 UTCEPSS rescore
  32. 2026-06-15 17:45 UTCEPSS rescore
  33. 2026-06-13 22:58 UTCEPSS rescore
  34. 2026-06-10 22:16 UTCEPSS rescore
  35. 2026-06-10 13:19 UTCEPSS rescore
  36. 2026-06-07 15:23 UTCEPSS rescore
  37. 2026-06-07 15:22 UTCEPSS rescore
  38. 2026-06-05 22:45 UTCEPSS rescore
  39. 2026-06-05 22:45 UTCEPSS rescore
  40. 2026-06-02 20:11 UTCEPSS rescore
  41. 2026-06-01 13:50 UTCEPSS rescore
  42. 2026-06-01 13:50 UTCEPSS rescore
  43. 2026-05-31 00:14 UTCEPSS rescore
  44. 2026-05-31 00:14 UTCEPSS rescore
  45. 2026-05-29 13:42 UTCEPSS rescore
  46. 2026-05-28 13:43 UTCEPSS rescore
  47. 2026-05-27 21:10 UTCEG score recompute
  48. 2026-05-27 21:10 UTCGHSA enrichment

Publicly available exploits

(2 references)

Working exploit code is in the public domain (1 Metasploit module). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitauxiliary/admin/http/wp_google_maps_sqli✓ verified
    First seen Apr 2, 2019

    WordPress Google Maps Plugin SQL Injection

    Open source ↗
  • Nucleihttp/cves/2019/CVE-2019-10692.yaml
    First seen Jan 1, 2019

    WordPress Google Maps <7.11.18 - SQL Injection

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2019-10692?
CVE-2019-10692 is a critical vulnerability published on April 2, 2019. 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.
When was CVE-2019-10692 disclosed?
CVE-2019-10692 was first published on April 2, 2019, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2019-10692 actively exploited?
CVE-2019-10692 is not currently on CISA's Known Exploited Vulnerabilities catalog. EchelonGraph's EG-KEV model classifies it as weaponized: a functional public exploit exists. FIRST EPSS estimates a 79% probability of exploitation in the next 30 days (99th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2019-10692?
CVE-2019-10692 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2019-10692?
A fix for CVE-2019-10692 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2019-10692

Explore →

Is Your Infrastructure Affected by CVE-2019-10692?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Book a Demo →Browse All CVEs