Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious XSS payload in plugin parameter
-
DeliveryDeliver crafted link to victim
-
ExploitVictim with active session opens link
-
ExecutionUnsanitized script executes in site origin
-
ImpactSteal session cookies or act as admin
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the Google Maps CP plugin (version 1.2.5 or earlier) to be installed and active on a WordPress site, and requires victim user interaction (UI:R) - the target must click a crafted link or load an attacker-controlled page that triggers the vulnerable output path. No authentication is required of the attacker (PR:N), so anyone can craft the payload, but the attack is limited by its dependence on social engineering to get a victim (ideally a privileged/authenticated user) to interact; without that interaction the XSS does not fire. The scope change (S:C) means the executed script can affect the broader WordPress session context rather than only the plugin component. |
| Impact | The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L indicates network-reachable, low-complexity, unauthenticated exploitation, but critically requires user interaction (UI:R) - a victim must click a crafted link or visit an attacker-influenced page. The scope-changed (S:C) low-impact triad across confidentiality, integrity, and availability produces the elevated 7.1 score typical of XSS affecting authenticated admin sessions. No EPSS score, KEV listing, POC, or SSVC decision data was provided, so exploitation probability cannot be quantified from the input; the absence of KEV and POC signals suggests this is not yet under active or widespread exploitation. Realistically this is a meaningful but not top-tier priority: it is unauthenticated and easy to trigger, but the UI:R requirement and low individual impacts mean it depends on social engineering rather than automatable mass exploitation. |
| Exploit ScenarioDerived | An attacker crafts a URL or page containing a malicious JavaScript payload targeting the vulnerable Google Maps CP parameter and lures a logged-in WordPress administrator to click it. When the victim's browser renders the unsanitized output, the script executes in the site's origin, allowing the attacker to steal session cookies, perform actions as the admin, or plant a persistent backdoor. No public proof-of-concept was identified in the provided data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jul 02, 2026
Stored/reflected Cross-Site Scripting in the Google Maps CP WordPress plugin (versions 1.2.5 and earlier, vendor CodePeople) lets an unauthenticated attacker inject malicious script that executes in a victim's browser after they interact with a crafted link or page. The flaw carries a CVSS 3.1 base score of 7.1 with a scope change, reflecting impact beyond the vulnerable component into the wider WordPress session. No public exploit identified at time of analysis, and it is not listed in CISA KEV.
RemediationAI
No vendor-released patch version is identified in the available data; a fixed release, if one exists, would be a version later than 1.2.5, but this is not independently confirmed. Administrators should monitor the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/codepeople-post-map/vulnerability/wordpress-google-maps-cp-plugin-1-2-5-cross-site-scripting-xss-vulnerability) and the WordPress plugin repository for an update and apply it immediately once released. As compensating controls until then, deploy a Web Application Firewall (such as Patchstack's or Wordfence) with XSS rules to filter script payloads on the plugin's parameters, restrict or disable the Google Maps CP plugin on high-value or admin-facing sites if the mapping feature is non-essential (side effect: maps stop rendering), and enforce a strict Content-Security-Policy that disallows inline scripts to blunt payload execution (side effect: may break other plugins relying on inline JS).
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Google Maps CP (plugin slug codepeople-post-map) is a WordPress plugin from CodePeople that embeds interactive Google Maps into posts and pages. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation), meaning user-controllable input is reflected or stored into HTML output without proper output encoding or input sanitization. Because it runs within WordPress, injected JavaScript executes in the context of the site's origin, giving access to the DOM, cookies, and any authenticated session active in the victim's browser. The CPE cpe:2.3:a:codepeople:google_maps_cp:*:*:*:*:*:*:*:* confirms all versions up to and including 1.2.5 are in scope.
Know when Google Maps Cp gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L
Unauthenticated network XSS (AV:N/PR:N) requiring victim click (UI:R); reflected script crosses into the WordPress session (S:C) with limited C/I/A impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Cross Site Scripting (XSS) in Google Maps CP <= 1.2.5 versions.
Executive ViewAI
Google Maps CP WordPress plugin (CodePeople, versions ≤1.2.5) contains a stored/reflected cross-site scripting vulnerability that allows unauthenticated attackers to inject malicious scripts into user browsers, compromising WordPress sessions and potentially enabling credential theft or malware distribution. Any organization running this plugin exposes its WordPress user base to account takeover and data exfiltration without user-facing indicators of compromise.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Disable plugin if non-critical to operations; (2) Deploy WAF rules blocking common XSS payloads (e.g., <script>, onerror=, javascript:) targeting the plugin's vulnerable parameters; (3) Enforce Content Security Policy headers (script-src 'self') to prevent injected script execution; (4) Monitor and log all plugin form submissions and API calls; (5) Require multi-factor authentication for WordPress admin accounts to limit session hijacking impact.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
EUVD-2026-41281
GHSA-6x98-crj7-pq94
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB