What is the CVSS score of EUVD-2026-39929?

EUVD-2026-39929 has a CVSS 3.1 base score of 6.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.2%.

CodePeople Post Map EUVD-2026-39929

| CVE-2026-13335 MEDIUM

Cross-site Scripting (XSS) (CWE-79)

2026-06-27 Wordfence

GHSA-xwv4-jx2p-x8xw

WordPress XSS Google Wordpress Plugin Codepeople Post Map For Google Maps Codepeople

6.4

CVSS 3.1 · Vendor: Wordfence

Severity by source

Vendor (Wordfence) PRIMARY

6.4 MEDIUM

AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

vuln.today AI

6.4 MEDIUM

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.

3.1 AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

4.0 AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

Analysis Generated

Jun 27, 2026 - 02:15 vuln.today

CVE Published

Jun 27, 2026 - 01:27 cve.org

MEDIUM 6.4

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.

AnalysisAI

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.

Technical ContextAI

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.

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.