dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-4429

MEDIUM · 6.4 CVSS v3.1 Published 2026-04-09
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
The OSM – OpenStreetMap plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'marker_name' and 'file_color_list' shortcode attribute of the [osm_map_v3] shortcode in all versions up to and including 6.1.15. This is 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 confidence

The OSM – OpenStreetMap WordPress plugin (versions up to 6.1.15) contains a stored XSS vulnerability in the [osm_map_v3] shortcode. Authenticated users with Contributor-level access or higher can inject arbitrary JavaScript via the 'marker_name' and 'file_color_list' attributes due to insufficient input sanitization and missing output escaping.

MitigationUpdate to the latest version of the OSM plugin and ensure all shortcode attributes are processed through proper sanitization functions (e.g., sanitize_text_field) and output escaping (e.g., esc_attr, esc_html) before rendering.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm OSM - OpenStreetMap plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'OSM - OpenStreetMap' in the list. Note the installed version number displayed next to the plugin name.
    Affected if The plugin is present and active in the WordPress installation
  2. Identify the installed plugin version
    In the plugins list, locate the version number under the OSM - OpenstreetMap plugin entry. Compare this version against the affected range: versions 6.1.15 and earlier are vulnerable.
    Affected if The installed version is 6.1.15 or any earlier version
  3. Verify user role permissions
    Navigate to Users > All Users in the WordPress admin. Review which users have the Contributor role or higher. Contributors can edit their own posts and may exploit this vulnerability if the plugin is present.
    Affected if There are users with Contributor-level access (or any user role above Contributor) who can create or edit content containing shortcodes
  4. Scan for vulnerable shortcode usage
    Search the WordPress database or site content (posts, pages, widgets) for the string '[osm_map_v3]' using phpMyAdmin, WP-CLI 'wp db search', or the WordPress admin's bulk search. Inspect any found shortcodes for 'marker_name' or 'file_color_list' attributes.
    Affected if The shortcode [osm_map_v3] is present in any published content, particularly with 'marker_name' or 'file_color_list' attributes that may contain unsanitized user input

A user is affected if the OSM - OpenStreetMap plugin version is 6.1.15 or earlier, Contributor-level or higher users exist on the site, and the vulnerable [osm_map_v3] shortcode with the 'marker_name' or 'file_color_list' attributes is in use.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the latest version of the OSM plugin and ensure all shortcode attributes are processed through proper sanitization functions (e.g., sanitize_text_field) and output escaping (e.g., esc_attr, esc_html) before rendering.

Recommended fix High confidence

Plugin version 6.1.16 or later

  1. 1. Log in to the WordPress admin dashboard with Contributor-level or higher privileges
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'OSM – OpenStreetMap' plugin
  4. 4. If an update is available, click 'Update Now' to upgrade to version 6.1.16 or later
  5. 5. After updating, verify the plugin version shows 6.1.16 or higher in the Plugins list
  6. 6. Test that the [osm_map_v3] shortcode functions correctly with the marker_name and file_color_list attributes

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4429 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-4429 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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