CVE-2026-39646
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 · uneditedImproper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in bozdoz Leaflet Map leaflet-map allows Stored XSS.This issue affects Leaflet Map: from n/a through <= 3.4.4.
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 confidenceStored Cross-site Scripting (XSS) vulnerability in the bozdoz Leaflet Map plugin (versions through 3.4.4) allows authenticated attackers to inject malicious JavaScript code through map data inputs that are not properly sanitized before being stored and rendered in web 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Leaflet Map plugin is installedLog into the WordPress admin dashboard, navigate to Plugins > Installed Plugins, and search for 'Leaflet Map' or 'bozdoz' to verify the plugin is present on the site.Affected if The plugin named 'Leaflet Map' or 'Leaflet Maps Marker' by bozdoz is found in the active or inactive plugins list.
-
Check installed plugin versionIn the WordPress plugins list, locate the Leaflet Map plugin entry and view the version number displayed under the plugin name. Compare this version to the affected range: any version 3.4.4 or lower is vulnerable.Affected if The installed version is 3.4.4 or any earlier version (e.g., 3.4.3, 3.4.0, 3.0.0, etc.).
-
Identify existing map configurationsNavigate to the Leaflet Map plugin settings or map management section in the WordPress admin sidebar. Look for any created maps or map configurations that contain custom parameters, markers, or configuration options that could accept user-supplied input.Affected if One or more maps have been created using the plugin with custom configuration options, markers, or location data that may contain unsanitized input.
-
Review user roles with map creation accessCheck WordPress user roles and permissions. Navigate to Users > All Users and also check if the Leaflet Map plugin has its own role or capability settings. Determine which user roles (administrator, editor, author, contributor) can create or edit maps.Affected if User roles other than Administrator (such as Editor, Author, or Contributor) have the ability to create, edit, or configure maps using the Leaflet Map plugin.
A user is affected if the Leaflet Map plugin version is 3.4.4 or lower, maps exist with custom configurations that could contain malicious input, and users with limited privileges can create or edit those maps.
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 dataImplement proper input validation and output encoding/sanitization on all user-supplied map data fields before storage and before rendering in the frontend. Consider adding Content Security Policy headers as defense-in-depth.
- Consultation4.0 h
- Implementation4.0 h
- Testing4.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 $3,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-39646 — 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-39646 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