CVE-2014-7182 json
Multiple cross-site scripting (XSS) vulnerabilities in the WP Google Maps plugin before 6.0.27 for WordPress allow remote attackers to inje…
published 2014-10-22 12 y ago modified 2026-06-17 4 mo ago also EUVD-2014-7059
- cvss
- 4.3
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 84%
- public exploits
- 0
- none known
Summary
Multiple cross-site scripting (XSS) vulnerabilities in the WP Google Maps plugin before 6.0.27 for WordPress allow remote attackers to inject arbitrary web script or HTML via the poly_id parameter in an (1) edit_poly, (2) edit_polyline, or (3) edit_marker action in the wp-google-maps-menu page to wp-admin/admin.php.
Exploit prediction
2.46% chance of exploitation in the next 30 days, higher than 84% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- packetstormsecurity.com http://packetstormsecurity.com/files/128694/WordPress-WP-Google-Maps-6.0.26-Cross-Site-Scripting.html referenced PoC, tagged "exploit" by a source, unverified
- htbridge.com https://www.htbridge.com/advisory/HTB23236 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 4.3 | AV:N/AC:M/Au:N/C:N/I:P/A:N |
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
packetstormsecurity.com
/files/128694/WordPress-WP-Google-Maps-6.0.26-Cross-Site-Scripting.html
exploit, third-party-advisory, vdb-entry
-
htbridge.com
/advisory/HTB23236
exploit
-
wordpress.org
/plugins/wp-google-maps/changelog
product, release-notes
-
securityfocus.com
/archive/1/533699/100/0/threaded
mailing-list, third-party-advisory, vdb-entry
-
securityfocus.com
/bid/70597
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2014-7182
- NVD CVE-2014-7182
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.