Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain control of referenced GeoJSON feed
-
DeliveryInject script into feature.properties fields
-
ExploitVisitor loads public choropleth map page
-
ExecutionTemplate token written to DOM unescaped
-
ImpactArbitrary script executes in victim's browser
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Execution The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation is gated by a specific, non-default deployment: a site administrator must have previously published a PUBLIC map using the combined [leaflet-map]+[leaflet-geojson]+[choropleth] shortcodes, and that choropleth map's GeoJSON src URL must resolve to a feed the attacker can control or influence - achieved through compromise of the external data host, a subdomain takeover of that host, or a site intentionally configured to consume an attacker-hosted feed. The concrete sink is the 'feature.properties[<template-token>]' value, which is rendered to the DOM without sufficient input sanitization or output escaping. Limiting factors: the attacker cannot inject without already controlling the upstream GeoJSON source, the map must be public, and the exact choropleth shortcode stack must be in use - maps not using attacker-influenceable external GeoJSON feeds are not exploitable. Although the attacker needs no WordPress authentication (PR:N), these configuration and data-source-control prerequisites account for the AC:H rating. |
| Impact | This is a moderate-severity, highly conditional stored DOM-based XSS rather than a broadly exploitable flaw. The supplied CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N, base 5.4) encodes the key tension: although PR:N marks the attacker as unauthenticated, AC:H reflects substantial preconditions, and the description confirms why - exploitation requires that a site administrator has already published a public map built from the [leaflet-map]+[leaflet-geojson]+[choropleth] shortcode combination AND that the map's GeoJSON src URL points at a feed the attacker controls (via compromise of the external data host, subdomain takeover, or a site deliberately pointing at an attacker feed). The attacker does not inject directly into WordPress; they poison the upstream data source. No CISA KEV listing and no EPSS score are provided, and there is no confirmed working exploit - the references are the Wordfence advisory and trac source-code lines, not a weaponized PoC. The vuln.today priority is 'this_month' (not act_now/emergency), consistent with a real but non-urgent, prerequisite-heavy issue. Net: low-to-moderate real-world risk dominated by whether any site actually runs the specific choropleth configuration against an attacker-influenceable feed, not a mass-exploitable web vulnerability. |
| Exploit ScenarioDerived | An administrator has published a public choropleth map whose GeoJSON data is pulled from an external URL. An attacker who gains control of that data source (e.g., via subdomain takeover or compromise of the external host) injects malicious script into a feature's properties, which the plugin writes into the page DOM without sanitization. Any visitor who loads the map page then executes the attacker's script in their browser. No confirmed working exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 29, 2026
Stored DOM-based cross-site scripting in the Extensions for Leaflet Map WordPress plugin through 5.4 lets unauthenticated attackers place script in a choropleth map's feature.properties template value, which then executes in visitors' browsers when the public map page is viewed. The flaw is tightly gated: an administrator must already have published a public map using the [leaflet-map]+[leaflet-geojson]+[choropleth] shortcode combination, and that map's GeoJSON src must point to a feed the attacker controls or can influence, such as through external host compromise, subdomain takeover, or an intentionally attacker-hosted feed. No public exploit has been identified at time of analysis; the CVSS 5.4 score and AC:H rating reflect these configuration and data-source-control prerequisites.
RemediationAI
Update the Extensions for Leaflet Map plugin from 5.4 or earlier to the referenced 6.0 release (https://downloads.wordpress.org/plugin/extensions-leaflet-map.6.0.zip), which is the fixed version identified in the available data; the Wordfence advisory is at https://www.wordfence.com/threat-intel/vulnerabilities/id/00c5eb87-3e08-489a-9b30-2fde4aa2274e?source=cve. The evidence does not describe a separate vendor workaround. Where the update cannot be applied immediately, the exposure is limited to public maps using the [leaflet-map]+[leaflet-geojson]+[choropleth] combination whose GeoJSON src resolves to an external or attacker-influenceable feed, so restricting choropleth maps to trusted, first-party GeoJSON sources or unpublishing such maps removes the described exploitation path.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The plugin integrates Leaflet maps into WordPress, and its choropleth extension consumes GeoJSON feature properties to build map output. The reported sink is the 'feature.properties[<template-token>]' value, which the plugin renders into the DOM without sufficient input sanitization or output escaping, a CWE-79 cross-site scripting class issue. References point to the 5.4 release's js/choropleth.js around lines 40 and 45 and php/choropleth.php around lines 47 and 80, indicating the data flows from PHP-side choropleth handling into client-side JavaScript rendering. The CPE cpe:2.3:a:hupe13:extensions_for_leaflet_map:*:*:*:*:*:*:*:* identifies the hupe13 WordPress plugin as the affected product. The trigger is not described beyond this parameter and rendering path; exploitation depends on the map being public, the specific shortcode stack being in use, and the GeoJSON source being attacker-influenceable.
Know when Extensions For Leaflet Map gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
Unauthenticated network injection but requires attacker control of the referenced GeoJSON feed plus a pre-existing public choropleth map, so AC:H; stored script runs in visitors' browsers (S:C, C:L/I:L), no availability impact.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
DescriptionCVE.org
The Extensions for Leaflet Map plugin for WordPress is vulnerable to Stored DOM-Based Cross-Site Scripting via the 'feature.properties[<template-token>]' parameter in all versions up to, and including, 5.4 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires that a site administrator has previously configured a public map using the [leaflet-map]+[leaflet-geojson]+[choropleth] shortcode combination whose GeoJSON src URL is one the attacker controls - for example, through compromise of an external data host, a subdomain takeover, or a site intentionally pointing at an attacker-hosted feed.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.
More in Extensions For Leaflet Map
View allStored/DOM-based cross-site scripting in the hupe13 "Extensions for Leaflet Map" WordPress plugin (all versions up to an
Stored Cross-Site Scripting in Extensions for Leaflet Map plugin for WordPress allows authenticated attackers with Contr
Unauth. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, low at
EUVD-2026-112681
GHSA-7vcm-wxx6-q65r
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB