CVE-2015-2755

AB Google Map Travel (AB-MAP) < 4.0 - Cross-Site Request Forgery to Cross-Site Scripting

2015-03-23 00:00
Kaustubh G. Padwad

Strategic Overview

Status
Patched in 4.0
Affected Version
< 4.0
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2015-2755
View all AB Google Map Travel (AB-MAP) vulnerabilities

At a glance

CVE-2015-2755 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the AB Google Map Travel (AB-MAP) WordPress plugin, affecting versions < 4.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.0; sites on affected versions should update now. Disclosed March 2015, reported by Kaustubh G. Padwad.

Vulnerability Overview

Multiple cross-site request forgery (CSRF) vulnerabilities in the AB Google Map Travel (AB-MAP) plugin before 4.0 for WordPress allow remote attackers to hijack the authentication of administrators for requests that conduct cross-site scripting (XSS) attacks via the (1) lat (Latitude), (2) long (Longitude), (3) map_width, (4) map_height, or (5) zoom (Map Zoom) parameter in the ab_map_options page to wp-admin/admin.php.

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 AB Google Map Travel (AB-MAP) < 4.0 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 AB Google Map Travel (AB-MAP) the fix is 4.0: builds < 4.0 are affected, anything from 4.0 onward is not.

Remediation

Update to version 4.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to AB Google Map Travel (AB-MAP): WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: AB Google Map Travel (AB-MAP) 4.0 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