MapSVG < 8.6.12 - Authenticated (Contributor+) Arbitrary File Download
Strategic Overview
- Status
- Patched in 8.6.12
- Affected Plugin
- MapSVG
- Affected Version
< 8.6.12- CVSS
- 4.3Medium
- Weakness type
- CWE-22 · Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
- CVE
CVE-2025-54748
At a glance
CVE-2025-54748 is a medium-severity Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') vulnerability in the MapSVG WordPress plugin, affecting versions < 8.6.12. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 8.6.12; sites on affected versions should update now. Disclosed July 2025, reported by Nguyễn Trung Kiên.
Vulnerability Overview
The MapSVG plugin for WordPress is vulnerable to Path Traversal in all versions up to 8.6.12 (exclusive). This makes it possible for authenticated attackers, with Contributor-level access and above, to read the contents of arbitrary files on the server, which can contain sensitive information.
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.
CWE-22: Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Reaching this weakness in MapSVG < 8.6.12 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.6.12: builds < 8.6.12 are affected, anything from 8.6.12 onward is not.
Remediation
Update to version 8.6.12, 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.6.12 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in MapSVG
- 8.8CVE-2025-47559: MapSVG < 8.7.4 Arbitrary File Upload
CVE-2025-47559 - 8.8CVE-2025-47561: MapSVG < 8.6.13 Privilege Esclation
CVE-2025-47561 - 7.5CVE-2026-59526: MapSVG <= 8.14.0 SQL Injection
CVE-2026-59526 - 7.5CVE-2025-54669: MapSVG < 8.7.4 SQL Injection
CVE-2025-54669 - 7.3CVE-2022-0592: MapSVG <= 6.2.19 SQL Injection
CVE-2022-0592 - 6.5CVE-2026-65451: MapSVG <= 8.14.0 SQL Injection
CVE-2026-65451 - 6.5CVE-2025-47562: MapSVG <= 8.5.34 Arbitrary Shortcode Execution
CVE-2025-47562 - 6.4CVE-2024-9544: MapSVG - All Kinds of Maps and Store… Stored XSS
CVE-2024-9544
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C