CVE-2015-9307

WP Google Map Plugin < 2.3.10 - Cross-Site Request Forgery

2015-08-21 00:00
Anonymous

Strategic Overview

Status
Patched in 2.3.10
Affected Version
< 2.3.10
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2015-9307
View all WP Maps – Google Maps,OpenStreetMap,Mapbox,Store Locator,Listing,Directory & Filters vulnerabilities

At a glance

CVE-2015-9307 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Maps WordPress plugin, affecting versions < 2.3.10. 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 2.3.10; sites on affected versions should update now. Disclosed August 2015.

Vulnerability Overview

The WP Google Map plugin before 2.3.10 for WordPress has CSRF in the add/edit location feature.

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-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in WP Maps < 2.3.10 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 2.3.10: builds < 2.3.10 are affected, anything from 2.3.10 onward is not.

Remediation

Update to version 2.3.10, 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 2.3.10 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