CVE-2022-25600

WP MAPS – Easiest & Most Advanced WordPress Plugin for Google Maps <= 4.2.3 - Cross-Site Request Forgery

2022-02-22 14:59
R3N0

Strategic Overview

Status
Patched in 4.2.4
Affected Version
< 4.2.4
CVSS
5.4Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-25600
View all WP Maps – Google Maps,OpenStreetMap,Mapbox,Store Locator,Listing,Directory & Filters vulnerabilities

At a glance

CVE-2022-25600 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Maps WordPress plugin, affecting versions < 4.2.4. It carries a CVSS score of 5.4 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 4.2.4; sites on affected versions should update now. Disclosed February 2022, reported by R3N0.

Vulnerability Overview

Cross-Site Request Forgery (CSRF) vulnerability affecting Delete Marker Category, Delete Map, and Copy Map functions in WP Google Map plugin (versions <= 4.2.3).

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 WP Maps < 4.2.4 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 WP Maps the fix is 4.2.4: builds < 4.2.4 are affected, anything from 4.2.4 onward is not.

Remediation

Update to version 4.2.4, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP Maps: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Maps 4.2.4 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