MapSVG – Vector maps, Image maps, Google Maps <= 8.16.1 - Authenticated (Contributor+) Arbitrary File Deletion
Strategic Overview
- Status
- Patched in 8.16.2
- Affected Plugin
- MapSVG – Vector maps, Image maps, Google Maps
- Affected Version
<= 8.16.1- CVSS
- 8.1High
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2026-111398
At a glance
CVE-2026-111398 is a high-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the MapSVG WordPress plugin, affecting versions <= 8.16.1. It carries a CVSS score of 8.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 8.16.2; sites on affected versions should update now. Disclosed October 2026, reported by hhhai.
Vulnerability Overview
The MapSVG – Vector maps, Image maps, Google Maps plugin for WordPress is vulnerable to Arbitrary File Deletion due to insufficient file path validation in all versions up to, and including, 8.16.1. This makes it possible for authenticated attackers, with contributor-level access and above, to delete arbitrary files on the server, which can easily lead to remote code execution when the right file is deleted (such as wp-config.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 interaction from a victim user. A successful exploit has high impact on integrity, availability.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in MapSVG <= 8.16.1 takes an account at Contributor level or above. Path traversal happens when user-controlled text is used to build a filesystem path without being constrained to an intended directory, so sequences like ../ walk the resolved path somewhere else.
Depending on the operation, it means reading files outside the intended folder — wp-config.php being the usual target — or writing to and deleting paths the web server can touch. For MapSVG the fix is 8.16.2: builds <= 8.16.1 are affected, anything from 8.16.2 onward is not.
Remediation
Update to version 8.16.2, or a newer patched version
How does WordSec protect against this?
An attacker needs Contributor 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.16.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in MapSVG – Vector maps, Image maps, Google Maps
- 8.8CVE-2026-111406: MapSVG Arbitrary File Upload
CVE-2026-111406 - 8.8CVE-2025-68562: MapSVG <= 8.7.3 Arbitrary File Upload
CVE-2025-68562 - 8.8CVE-2025-32682: MapSVG Lite <= 8.6.4 Arbitrary File Upload
CVE-2025-32682 - 7.5CVE-2026-59527: MapSVG SQL Injection
CVE-2026-59527 - 7.2CVE-2026-82852: MapSVG – Vector maps, Image maps, Google Maps SSRF
CVE-2026-82852 - 7.2CVE-2026-65455: MapSVG Arbitrary File Upload
CVE-2026-65455 - 7.2CVE-2026-1771: MapSVG <= 8.14.0 Arbitrary File Upload
CVE-2026-1771 - 6.5CVE-2026-111399: MapSVG SQL Injection
CVE-2026-111399
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C