CVE-2024-9544

MapSVG - All Kinds of Maps and Store Locator for WordPress <= 8.6.4 - Authenticated (Contributor+) Stored Cross-Site Scripting

2025-05-21 21:10
Mo'men Saad

Strategic Overview

Status
Unpatched
Affected Plugin
MapSVG
Affected Version
<= 8.6.4
CVSS
6.4Medium
Weakness type
CWE-434 · Unrestricted Upload of File with Dangerous Type
CVE
CVE-2024-9544
View all MapSVG vulnerabilities

At a glance

CVE-2024-9544 is a medium-severity Unrestricted Upload of File with Dangerous Type vulnerability in the MapSVG WordPress plugin, affecting versions <= 8.6.4. It carries a CVSS score of 6.4 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed May 2025, reported by Mo'men Saad.

Vulnerability Overview

The MapSVG plugin for WordPress is vulnerable to Stored Cross-Site Scripting via SVG File uploads in all versions up to, and including, 8.6.4 due to insufficient input sanitization and output escaping. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses the SVG file.

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-434: Unrestricted Upload of File with Dangerous Type

Reaching this weakness in MapSVG <= 8.6.4 takes an account at Contributor level or above. An unrestricted file upload lets a caller store a file whose type or destination the application does not properly constrain.

If an uploaded file lands anywhere the server will execute, the flaw becomes remote code execution and the site should be treated as fully compromised. No fixed build of this plugin is recorded for MapSVG yet, so installs running <= 8.6.4 stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

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. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Firewall
  • Scanner
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-9544https://www.wordfence.com/threat-intel/vulnerabilities/id/3ec77f96-c73a-44f7-afa2-673f68ee3582https://nvd.nist.gov/vuln/detail/CVE-2024-9544

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C