CVE-2026-1771

MapSVG <= 8.14.0 - Authenticated (Administrator+) Arbitrary File Upload via '/mapsvg/v1/svgfile' Endpoint

2026-07-20 19:29
san6051

Strategic Overview

Status
Patched in 8.14.1
Affected Version
<= 8.14.0
CVSS
7.2High
Weakness type
CWE-20 · Improper Input Validation
CVE
CVE-2026-1771
View all MapSVG – Vector maps, Image maps, Google Maps vulnerabilities

At a glance

CVE-2026-1771 is a high-severity Improper Input Validation vulnerability in the MapSVG WordPress plugin, affecting versions <= 8.14.0. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Administrator level or above. The issue is fixed in version 8.14.1; sites on affected versions should update now. Disclosed July 2026, reported by san6051.

Vulnerability Overview

The MapSVG plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the SVGFile constructor in all versions up to, and including, 8.14.0 This is due to an incorrect conditional check that prevents file validation from taking place. This makes it possible for authenticated attackers, with Administrator-level access and above, to upload arbitrary files on the affected site's server which may make remote code execution possible.

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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-20: Improper Input Validation

Reaching this weakness in MapSVG <= 8.14.0 takes an account at Administrator level or above. Improper input validation means the application accepts input without confirming it has the form, type or range the code downstream assumes.

The concrete impact depends on where the unvalidated value lands, which is why records in this class range from cosmetic bugs to full compromise. For MapSVG the fix is 8.14.1: builds <= 8.14.0 are affected, anything from 8.14.1 onward is not.

Remediation

Update to version 8.14.1, or a newer patched version

How does WordSec protect against this?

An attacker needs Administrator access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: MapSVG 8.14.1 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