CVE-2026-13335
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe CodePeople Post Map for Google Maps WordPress plugin fails to properly sanitize the 'cpm_point' post meta input and escape it during output, allowing authenticated users with Contributor-level permissions to inject malicious JavaScript that executes when other users view affected pages.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check plugin versionIn WordPress admin, go to Plugins > Installed Plugins > CodePeople Post Map for Google Maps and note the version number displayed. Alternatively, check the plugin's main PHP file (typically in wp-content/plugins/post-map-for-google-maps/) for the Version header in the plugin comment block.Affected if The installed version is 1.2.6 or lower.
-
Verify plugin is activeIn WordPress admin, go to Plugins > Installed Plugins and confirm that CodePeople Post Map for Google Maps shows as 'Active'.Affected if The plugin is active and version is 1.2.6 or lower.
-
Query database for cpm_point meta entriesRun a SQL query on the WordPress database: SELECT post_id, meta_value FROM wp_postmeta WHERE meta_key = 'cpm_point'. Inspect the meta_value field for any script tags, javascript: URLs, onload/onerror attributes, or other XSS payloads.Affected if Any cpm_point meta values contain unescaped HTML, script tags, or JavaScript event handlers.
-
Inspect post content for stored XSSView pages or posts that use the Google Maps plugin. View the page source and check if the cpm_point data appears unescaped (visible as raw HTML tags rather than escaped entities).Affected if The cpm_point data renders as executable JavaScript or displays raw HTML tags in the page source.
If the plugin version is 1.2.6 or lower and active, and the cpm_point meta field contains any injected script tags or unescaped HTML/JavaScript, the environment is affected by this stored XSS vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataUpdate the plugin to a version beyond 1.2.6 that implements proper input sanitization using WordPress functions like sanitize_text_field() and output escaping with esc_html() or esc_attr().
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-13335 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-13335 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data