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

CVE-2026-4389

MEDIUM · 6.4 CVSS v3.1 Published 2026-03-26
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 DSGVO snippet for Leaflet Map and its Extensions plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the `leafext-cookie-time` and `leafext-delete-cookie` shortcodes in all versions up to, and including, 3.1. This is due to insufficient input sanitization and output escaping on user supplied attributes (`unset`, `before`, `after`). 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 Leaflet Map WordPress plugin versions up to 3.1 contain a stored XSS vulnerability in the DSGVO cookie-related shortcodes. Authenticated contributors can inject malicious JavaScript via the `unset`, `before`, and `after` attributes of the `leafext-cookie-time` and `leafext-delete-cookie` shortcodes due to missing input sanitization and output escaping.

MitigationUpgrade to version 3.2 or later which includes proper input sanitization using functions like `esc_attr()` and output escaping. Until then, restrict contributor-level user permissions and audit existing content for malicious shortcodes.

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 Leaflet Map plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Leaflet Map' in the list. Note the installed version number.
    Affected if Plugin is installed and version is 3.1 or lower
  2. Verify the plugin version
    Check the plugin version against the affected range. The plugin version is displayed on the plugins page next to the plugin name. Compare your version to 'up to 3.1' (affected) versus '3.2 and later' (fixed).
    Affected if Installed version is 3.1 or earlier
  3. Check for vulnerable shortcode usage in content
    Search your WordPress database or content for the shortcodes 'leafext-cookie-time' and 'leafext-delete-cookie'. You can use WP-CLI: wp-cli search-replace --report-changed-only or check posts/pages/custom post types via database query for these shortcode strings.
    Affected if Either shortcode is present in any published content
  4. Inspect shortcode attributes for unsanitized input
    If the shortcodes are found, examine the 'unset', 'before', and 'after' attributes. Look for any raw or potentially malicious values that were not escaped. Check the raw database content or shortcode output in the editor.
    Affected if The 'unset', 'before', or 'after' attributes contain unsanitized user-supplied values that could execute as JavaScript
  5. Identify contributor-level users
    In WordPress admin, go to Users and review user roles. Contributor role can exploit this vulnerability. Check if any users have the Contributor role or higher (Author, Editor, Admin) who could create or edit content with these shortcodes.
    Affected if There are users with Contributor role or higher who can create or edit content

A user is affected if the Leaflet Map plugin version is 3.1 or earlier AND any content contains the vulnerable shortcodes with the 'unset', 'before', or 'after' attributes present.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to version 3.2 or later which includes proper input sanitization using functions like `esc_attr()` and output escaping. Until then, restrict contributor-level user permissions and audit existing content for malicious shortcodes.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-4389 — 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-4389 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