CVE-2026-7464 json
WP Google Maps Integration <= 1.2 - Reflected Cross-Site Scripting via 'page' Parameter
published 2026-05-12 5 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-29415
- cvss
- 6.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 11%
- public exploits
- 0
- none known
Summary
The WP Google Maps Integration plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via the `page` parameter in all versions up to, and including, 1.2. This is due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick an administrator into performing an action such as clicking on a link.
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 5 mo ago
Exploit prediction
0.21% chance of exploitation in the next 30 days, higher than 11% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| 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
- trapesium WP Google Maps Integration
Classification
- Weakness
-
- CWE-79 Improper Neutralization of Input During Web Page Generation
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/bd9ef48f-b501-4fca-a6a5-78452c316497?source=cve
- plugins.trac.wordpress.org /browser/wp-google-maps-integration/trunk/admin/partials/category/category-table-display.php#L48
- plugins.trac.wordpress.org /browser/wp-google-maps-integration/trunk/admin/partials/marker/marker-table-display.php#L46
- plugins.trac.wordpress.org /browser/wp-google-maps-integration/trunk/admin/partials/route/route-table-display.php#L42
- plugins.trac.wordpress.org /browser/wp-google-maps-integration/trunk/admin/partials/map/map-table-display.php#L42
Sources
- CVE List CVE-2026-7464
- NVD CVE-2026-7464
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.