# CVE-2024-11847: WP SVG Upload <= 1.0.0 - Author+ Stored XSS via SVG

> Authors can upload malicious SVG files to execute stored XSS attacks in the WP SVG Upload WordPress plugin.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Mar 2025
- **Updated:** 26 Mar 2025
- **Also known as:** GHSA-v2rr-fhv8-mx74

## What is CVE-2024-11847?

CVE-2024-11847 is a medium-severity cross-site scripting vulnerability in Unknown wp-svg-upload, published on 26 Mar 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

The wp-svg-upload WordPress plugin through 1.0.0 does not sanitize SVG file contents, which enables users with at least the author role to SVG with malicious JavaScript to conduct Stored XSS attacks.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2024-11847?

2 open source packages ship an affected version, including digimix/wp-svg-upload. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `digimix/wp-svg-upload` | Packagist | All versions to 1.0.0 | None |
| `digimix/wp-svg-upload` | Packagist | All versions to 1.0.0 | None |

Products: Wp Svg Upload Project  Wp Svg Upload.

## How do I fix CVE-2024-11847?

No fix has been published for CVE-2024-11847 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-11847 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11847 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-11847 and fix it if it is affected.

What it is: CVE-2024-11847 is a medium-severity cross-site scripting vulnerability in Unknown wp-svg-upload, published on 26 Mar 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-11847 exists.

Affected packages and fixed versions:
- digimix/wp-svg-upload (Packagist): affected all versions up to 1.0.0; no fix listed
- digimix/wp-svg-upload (Packagist): affected all versions up to 1.0.0; no fix listed

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-2024-11847/ (Markdown: https://insights.sbomify.com/CVE-2024-11847/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-11847
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-11847
- OSV: https://osv.dev/vulnerability/CVE-2024-11847

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-11847/
Summaries are generated and may contain mistakes; the official description above is the record.