Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessObtain Contributor-level WordPress account
-
DeliveryInject script payload into cpm_point post meta
-
ExploitPayload persisted to WordPress database
-
ExecutionPrivileged user visits injected post page
-
PersistStored XSS executes in victim browser
-
ImpactExfiltrate session token or perform admin actions
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 a valid WordPress user account at Contributor level or higher - unauthenticated attackers cannot exploit this vulnerability. The CodePeople Post Map for Google Maps plugin must be installed, active, and at version 1.2.6 or earlier. The attacker must have the capability to create or edit WordPress posts and set the 'cpm_point' post meta value, which is standard functionality available to Contributors. Exploitation is further limited by the requirement that a victim (ideally a privileged user such as an Editor or Administrator) must visit the page containing the injected map point for the payload to execute. Sites where Contributor-level access is restricted to fully trusted internal users, or where no Contributor-or-above accounts exist for external parties, face substantially lower realistic risk despite the network-accessible CVSS vector. |
| Impact | The CVSS 3.1 score of 6.4 (Medium) with vector AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N accurately reflects the key risk dynamics. The PR:L constraint is the primary limiting factor: exploitation is gated on possessing at minimum a WordPress Contributor-level account, which prevents unauthenticated remote exploitation. However, in multi-author WordPress environments - news sites, community blogs, CMS platforms with open contributor registration - this bar is frequently met by a large user population, making the effective attack surface substantially broader than a pure PR:H flaw. The S:C flag is significant: the injected script executes in the victim's browser context, enabling theft of session tokens or forced administrative actions if an admin visits the page, which is a realistic privilege-escalation path in WordPress. No EPSS score was provided in the available data, KEV listing is absent, and no POC code has been identified, suggesting this is not currently subject to broad automated exploitation. The WordPress SVN changeset reference indicates an upstream fix has been committed, reducing remediation friction. Real-world priority is moderate: highest for multi-author WordPress deployments with external contributor access; lower for single-author or tightly controlled sites. |
| Exploit ScenarioDerived | An attacker registers or compromises a Contributor-level WordPress account on a target site running CodePeople Post Map for Google Maps 1.2.6 or earlier. The attacker creates a post embedding a Google Map and sets the 'cpm_point' meta field to a value containing a malicious JavaScript payload (e.g., a script that exfiltrates the visitor's session cookie to an attacker-controlled endpoint). When an administrator reviews or visits the published post, the stored script executes silently in their browser, delivering the admin session token to the attacker and enabling full site takeover. No public POC has been identified, but the technique is well-understood for WordPress stored XSS flaws of this class. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 27, 2026
Stored Cross-Site Scripting in the CodePeople Post Map for Google Maps WordPress plugin (versions through 1.2.6) permits authenticated Contributor-level users to persist malicious JavaScript payloads via the 'cpm_point' post meta field. The CVSS S:C (Scope Changed) flag confirms the injected scripts execute in victim browser sessions beyond the plugin's own context, enabling session hijacking, credential theft, or unauthorized admin actions against any user who visits an injected page. No confirmed active exploitation appears in CISA KEV, and no public exploit code has been identified at time of analysis.
RemediationAI
An upstream fix has been committed to the WordPress plugin SVN repository at changeset revision 3586404 (https://plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&old=3586404%40codepeople-post-map&new=3586404%40codepeople-post-map); however, a patched tagged release version beyond 1.2.6 is not independently confirmed from the available data - administrators should monitor the WordPress plugin directory for an updated release and apply it immediately upon publication. As an interim compensating control, restrict Contributor-level account creation: disable open registration or audit all existing contributors for trust, since exploitation requires at minimum that privilege level. Sites where the map functionality is not actively used should deactivate and remove the plugin entirely - this eliminates the attack surface completely with the trade-off of losing embedded map features. If the plugin must remain active, Web Application Firewall rules targeting the 'cpm_point' parameter for script injection patterns (e.g., Wordfence's built-in rules) can reduce exploitation likelihood, though WAF bypasses exist and this is not a substitute for patching.
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
The vulnerability affects the CodePeople Post Map for Google Maps WordPress plugin by Codepeople (CPE: cpe:2.3:a:codepeople:codepeople_post_map_for_google_maps:*:*:*:*:*:*:*:*), a plugin that allows authors to embed Google Maps with custom map points into WordPress posts via post meta. The root cause is CWE-79 (Improper Neutralization of Input During Web Page Generation), where user-supplied data stored in the 'cpm_point' post meta field is written to the database and later rendered in page output without adequate sanitization or escaping. The Wordfence disclosure references multiple vulnerable output locations in include/functions.php at lines 132, 163, 710, 712, 713, and 881, indicating the unsanitized meta value is echoed in several rendering paths. As a stored (persistent) XSS variant, the injected payload survives across page loads and executes automatically for every visitor, distinguishing it from reflected XSS which requires per-request attacker delivery.
Know when Codepeople Post Map For Google Maps 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:L/UI:N/S:C/C:L/I:L/A:N
Network-accessible stored XSS requires Contributor auth (PR:L); payload auto-executes on page visit scoping impact to victim browser (S:C); no server-side confidentiality or availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The CodePeople Post Map for Google Maps plugin for WordPress is vulnerable to Stored Cross-Site Scripting via 'cpm_point' Post Meta in all versions up to, and including, 1.2.6 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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-39929
GHSA-xwv4-jx2p-x8xw
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB