CVE-2025-13364
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 WP Maps – Store Locator,Google Maps,OpenStreetMap,Mapbox,Listing,Directory & Filters plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'put_wpgm' shortcode in all versions up to, and including, 4.8.7. This is due to insufficient input sanitization and output escaping on user-supplied shortcode attributes. 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 confidenceThis is a Stored Cross-Site Scripting (XSS) vulnerability in the WP Maps WordPress plugin. The 'put_wpgm' shortcode does not properly sanitize user-supplied attributes before outputting them, allowing authenticated contributors+ to inject malicious JavaScript. When other users view pages containing the injected shortcode, the script executes in their browsers.
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.
-
Verify WP Maps plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'WP Maps' in the list. Note whether it is installed and whether it is active.Affected if WP Maps plugin is installed and active
-
Find installed WP Maps versionIn the Plugins list, find WP Maps and read the version number displayed beneath the plugin name. Compare this to version 4.8.7 - versions 4.8.7 and earlier are within the affected range.Affected if Installed version is 4.8.7 or earlier
-
Identify use of put_wpgm shortcodeSearch your WordPress posts, pages, and custom post types for the shortcode '[put_wpgm' using the WordPress admin search or a database query. This shortcode processes map display options.Affected if The put_wpgm shortcode is present in any published content
-
Inspect shortcode attributes for unsanitized outputExamine the actual shortcode usage in the content editor or database. Look for any attributes that contain user-supplied values (such as custom markers, labels, or parameters) that might be reflected in the page HTML without proper escaping.Affected if Shortcode contains custom attributes with unsanitized user input that could be injected into page output
A user is affected if WP Maps version 4.8.7 or earlier is installed, the plugin is active, and the put_wpgm shortcode with unsanitized attributes exists in published content.
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 WP Maps plugin to a version beyond 4.8.7. If no patched version is available, remove the plugin or restrict shortcode usage to trusted users only until a fix is released.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13364 — 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-2025-13364 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