CVE-2021-39346 json
Google Maps Easy <= 1.9.33 Authenticated Stored Cross-Site Scripting
published 2021-11-01 5 y ago modified 2026-06-17 4 mo ago also EUVD-2021-25707
- cvss
- 4.8
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.0%
- EPSS 1.0% chance of exploitation in 30 days, percentile 62%
- public exploits
- 0
- none known
Summary
The Google Maps Easy WordPress plugin is vulnerable to Stored Cross-Site Scripting due to insufficient input validation and sanitization via several parameters found in the ~/modules/marker_groups/views/tpl/mgrEditMarkerGroup.php file which allowed attackers with administrative user access to inject arbitrary web scripts, in versions up to and including 1.9.33. This affects multi-site installations where unfiltered_html is disabled for administrators, and sites where unfiltered_html is disabled.
Patch / fix
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 19 mo ago
Exploit prediction
0.97% chance of exploitation in the next 30 days, higher than 62% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- github.com https://github.com/BigTiger2020/word-press/blob/main/Google%20Maps%20Easy.md referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.8 | CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N |
| NVD | 2.0 | 2.1 | AV:N/AC:H/Au:S/C:N/I:P/A:N |
Affected products
- Google Maps Easy Google Maps Easy
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
plugins.trac.wordpress.org
/changeset/2620851/google-maps-easy/trunk/modules/marker_groups/views/tpl/mgrEditMarkerGroup.php
patch, third-party-advisory
-
github.com
/BigTiger2020/word-press/blob/main/Google%20Maps%20Easy.md
exploit, third-party-advisory
-
wordfence.com
/vulnerability-advisories/#CVE-2021-39346
third-party-advisory
Sources
- CVE List CVE-2021-39346
- NVD CVE-2021-39346
Fencer Vulns 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.