CVE-2023-6627 json
WP Go Maps < 9.0.28 - Unauthenticated Stored XSS
published 2y ago modified 5mo ago also EUVD-2023-58850
- cvss
- 6.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 50%
- public exploits
- 0
- none known
Summary
The WP Go Maps (formerly WP Google Maps) WordPress plugin before 9.0.28 does not properly protect most of its REST API routes, which attackers can abuse to store malicious HTML/Javascript on the site.
Patch / fix
- Unknown WP Go Maps (formerly WP Google Maps) 9.0.28
Is CVE-2023-6627 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 2y ago
Exploit prediction
0.62% chance of exploitation in the next 30 days, higher than 50% of all scored CVEs (FIRST EPSS, 2026-11-21).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/f5687d0e-98ca-4449-98d6-7170c97c8f54 referenced PoC, tagged "exploit" by a source, unverified
- wpscan.com https://wpscan.com/blog/stored-xss-fixed-in-wp-go-maps-9-0-28/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| NVD | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
| CNA | 3.1 | 6.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N |
Affected products
- Unknown WP Go Maps (formerly WP Google Maps)
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
-
wpscan.com
/vulnerability/f5687d0e-98ca-4449-98d6-7170c97c8f54
exploit, vdb-entry, technical-description, third-party-advisory
-
wpscan.com
/blog/stored-xss-fixed-in-wp-go-maps-9-0-28/
technical-description, exploit, third-party-advisory
Sources
- CVE List CVE-2023-6627
- NVD CVE-2023-6627
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.