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

CVE-2026-57380

HIGH · 7.1 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges 5 weeks old

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
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in hupe13 Extensions for Leaflet Map extensions-leaflet-map allows DOM-Based XSS.This issue affects Extensions for Leaflet Map: from n/a through <= 5.1.

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 · moderate confidence

DOM-Based Cross-site Scripting (XSS) vulnerability in hupe13 Extensions for Leaflet Map (versions <= 5.1). The vulnerability allows attackers to inject malicious JavaScript code through user-controllable input that is directly inserted into the webpage DOM without proper sanitization or output encoding.

MitigationImplement proper output encoding/sanitization for all user inputs before rendering them in the DOM. Review and secure all JavaScript code paths that process user input and manipulate the DOM, particularly within Leaflet Map rendering logic.

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
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Identify if hupe13 Extensions for Leaflet Map is installed
    Check your WordPress plugin list, CMS extension manager, or website source code for the presence of 'hupe13' or 'Extensions for Leaflet Map' plugin/extension
    Affected if The extension is found in your installation
  2. Determine the installed version number
    Access the plugin metadata through your CMS admin panel, check the plugin header comments in the main PHP/JavaScript file, or review your package.json/composer.json if using a package manager
    Affected if The version is 5.1 or lower, or if version information cannot be determined but the plugin is present
  3. Inspect JavaScript files for DOM manipulation with user input
    Examine the extension JavaScript files (typically in /js/ or /assets/js/ directory) for code that uses document.write(), innerHTML, outerHTML, or similar DOM insertion methods with parameters that could be user-controlled (e.g., query parameters, form inputs, URL fragments)
    Affected if Code directly inserts unsanitized user input into the DOM, particularly within Leaflet map initialization or marker/popup rendering functions
  4. Check for user-controllable input endpoints
    Review any frontend code that reads URL parameters, hash fragments, or form submissions and passes them to Leaflet map functions such as L.map(), L.marker(), or popup content without encoding
    Affected if User-controllable data flows directly into Leaflet rendering functions without sanitization
  5. Verify if custom Leaflet configurations accept user input
    Look for custom map configurations, shortcodes, or widgets where administrators can specify values that get rendered in the map interface
    Affected if The extension allows end users to provide input that appears in the map output without output encoding

If hupe13 Extensions for Leaflet Map version 5.1 or lower is installed and user-controllable input can reach the DOM through Leaflet map rendering without sanitization, the environment is affected by this DOM-based XSS vulnerability.

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

Implement proper output encoding/sanitization for all user inputs before rendering them in the DOM. Review and secure all JavaScript code paths that process user input and manipulate the DOM, particularly within Leaflet Map rendering logic.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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