WP Google Map Plugin <= 4.0.9 - Cross-Site Request Forgery to PHP Object Injection

2019-09-21 00:00
Anonymous

Strategic Overview

Status
Patched in 4.1.0
Affected Plugin
WP Maps – Google Maps,OpenStreetMap,Mapbox,Store Locator,Listing,Directory & Filters
Affected Version
< 4.1.0
CVSS
8.8High
Weakness type
CWE-502 · Deserialization of Untrusted Data
CVE
CVE pending
View all WP Maps – Google Maps,OpenStreetMap,Mapbox,Store Locator,Listing,Directory & Filters vulnerabilities

At a glance

This record tracks a high-severity Deserialization of Untrusted Data vulnerability in the WP Maps WordPress plugin, affecting versions < 4.1.0. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 4.1.0; sites on affected versions should update now. Disclosed September 2019.

Vulnerability Overview

The WP Google Map Plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 4.1.0. This is due to missing or incorrect nonce validation on the save() function. This makes it possible for unauthenticated attackers to exploit PHP Object Injection 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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-502: Deserialization of Untrusted Data

WP Maps < 4.1.0 carries this weakness at save(), and reaching it takes a caller who can reach the endpoint. Deserialization of untrusted data means the application reconstructs objects from input a caller controls, letting the attacker choose which classes get instantiated and what their properties hold.

A workable chain turns deserialization into file writes, deletions or code execution, depending on what the loaded classes do in their magic methods. For WP Maps the fix is 4.1.0: builds < 4.1.0 are affected, anything from 4.1.0 onward is not.

Remediation

Update to version 4.1.0, 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. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: WP Maps 4.1.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/a5ba9285-9f41-44dd-83c7-e9c377d9de51

Related records

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