CVE-2021-24643

WP Map Block – Gutenberg Map Block for Google Map and OpenStreet Map <= 1.2.2 - Stored Cross-Site Scripting

2021-08-25 00:00
apple502j

Strategic Overview

Status
Patched in 1.2.3
Affected Version
< 1.2.3
CVSS
5.4Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE-2021-24643
View all WP Map Block – Google Maps, OpenStreetMap, Mapbox, Store & Shop Locator, Directory, Listings & Filters vulnerabilities

At a glance

CVE-2021-24643 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WP Map Block WordPress plugin, affecting versions < 1.2.3. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). The issue is fixed in version 1.2.3; sites on affected versions should update now. Disclosed August 2021, reported by apple502j.

Vulnerability Overview

The WP Map Block WordPress plugin before 1.2.3 does not escape some attributes of the WP Map Block, which could allow users with a role as low as contributor to perform Stored Cross-Site Scripting attacks.

Technical Analysis

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

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in WP Map Block < 1.2.3 takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For WP Map Block the fix is 1.2.3: builds < 1.2.3 are affected, anything from 1.2.3 onward is not.

Remediation

Update to version 1.2.3, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C