CVE-2026-65455 WordPress MapSVG plugin <= 8.14.0 - Arbitrary File Upload vulnerability
Critical 9.1
Published
Updated
Check this codebase for CVE-2026-65455 and fix it if it is affected.
What it is: CVE-2026-65455 is a critical vulnerability in MapSVG, published on 23 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-65455 in the wild and no public exploit code.
Affected product: MapSVG. No package-level version data is available, so check the vendor advisory linked from the reference page.
Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.
Reference: https://insights.sbomify.com/CVE-2026-65455/ (Markdown: https://insights.sbomify.com/CVE-2026-65455/index.md)
Administrators can upload arbitrary files, potentially leading to remote code execution on WordPress sites using the MapSVG plugin.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-65455?
CVE-2026-65455 is a critical vulnerability in MapSVG, published on 23 Jul 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
Administrator Arbitrary File Upload in MapSVG <= 8.14.0 versions.
Weakness: CWE-434
Which versions are affected by CVE-2026-65455?
How do I fix CVE-2026-65455?
No fix has been published for CVE-2026-65455 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-65455 being exploited?
There is no known exploitation of CVE-2026-65455 in the wild and no public exploit code.
Sources
Also known as GHSA-wqmx-26v8-w3xg.