CVE-2019-1000003

MapSVG Lite < 3.3.0 - Cross-Site Request Forgery

2019-01-08 00:00
Rob Skilling (DXW)

Strategic Overview

Status
Patched in 3.3.0
Affected Version
< 3.3.0
CVSS
6.1Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2019-1000003
View all MapSVG – Vector maps, Image maps, Google Maps vulnerabilities

At a glance

CVE-2019-1000003 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the MapSVG WordPress plugin, affecting versions < 3.3.0. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.3.0; sites on affected versions should update now. Disclosed January 2019, reported by Rob Skilling (DXW).

Vulnerability Overview

MapSVG MapSVG Lite version 3.2.3 contains a Cross Site Request Forgery (CSRF) vulnerability in REST endpoint /wp-admin/admin-ajax.php?action=mapsvg_save that can result in an attacker modifying post data, including embedding javascript. This attack appears to be exploitable via a victim who must be logged in to WordPress as an admin, and click a link. This vulnerability appears to have been fixed in 3.3.0 and later.

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 MapSVG < 3.3.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 MapSVG the fix is 3.3.0: builds < 3.3.0 are affected, anything from 3.3.0 onward is not.

Remediation

Update to version 3.3.0, or a newer patched version

How does WordSec protect against this?

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