CVE-2021-24467

Leaflet Map < 3.0.0 - Cross-Site Request Forgery to Stored Cross-Site Scripting

2021-07-01 00:00

Strategic Overview

Status: Patched in 3.0.0
Affected Plugin: Leaflet Map
Affected Version: <= 2.23.3
CVSS: 6.1Medium
Weakness type: CWE-352 · Cross-Site Request Forgery (CSRF)
CVE: CVE-2021-24467

At a glance

CVE-2021-24467 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Leaflet Map WordPress plugin, affecting versions <= 2.23.3. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.0.0; sites on affected versions should update now. Disclosed July 2021, reported by apple502j.

Vulnerability Overview

The Leaflet Map WordPress plugin before 3.0.0 does not verify the CSRF nonce when saving its settings, which allows attackers to make a logged in admin update the settings via a Cross-Site Request Forgery attack. This could lead to Cross-Site Scripting issues by either changing the URL of the JavaScript library being used, or using malicious attributions which will be executed in all page with an embed map from the plugin

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Leaflet Map <= 2.23.3 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Leaflet Map the fix is 3.0.0: builds <= 2.23.3 are affected, anything from 3.0.0 onward is not.

Remediation

Update to version 3.0.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Leaflet Map: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Leaflet Map 3.0.0 closes this, and updating the plugin is the step that ends it.

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2021-24467 https://www.wordfence.com/threat-intel/vulnerabilities/id/b0d7e56d-453f-4df0-8cf5-32d8bafc60d5 https://nvd.nist.gov/vuln/detail/CVE-2021-24467

Related records

Other vulnerabilities in Leaflet Map

CVSS Vector

6.1

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

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeChanged
ConfidentialityLow
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/