CVE-2023-28172

WP Google Map Plugin <= 4.4.2 - Cross-Site Request Forgery via delete()

2023-03-13 00:00
Rafie Muhammad

Strategic Overview

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

At a glance

CVE-2023-28172 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Maps WordPress plugin, affecting versions <= 4.4.2. 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.4.3; sites on affected versions should update now. Disclosed March 2023, reported by Rafie Muhammad.

Vulnerability Overview

The WP Google Map Plugin plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.4.2. This is due to missing or incorrect nonce validation on the delete() function of the WPGMP_Model_Group_Map, WPGMP_Model_Location, and WPGMP_Model_Map classes. This makes it possible for unauthenticated attackers to delete a location, category, or map via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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)

WP Maps <= 4.4.2 carries this weakness at delete(), and reaching it 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.4.3: builds <= 4.4.2 are affected, anything from 4.4.3 onward is not.

Remediation

Update to version 4.4.3, 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.4.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2023-28172https://www.wordfence.com/threat-intel/vulnerabilities/id/71f58781-3fb3-4eba-8e5a-f98f006f4607https://nvd.nist.gov/vuln/detail/CVE-2023-28172

Related records

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