# CVE-2023-7086: SVG Uploads Support <= 2.1.1 - Author+ Stored XSS via SVG

> Attackers with Author role can upload malicious SVG files to execute arbitrary scripts in victim browsers via stored XSS.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 15 May 2025
- **Updated:** 17 May 2025
- **Also known as:** GHSA-vxgw-vvr8-p42m

## What is CVE-2023-7086?

CVE-2023-7086 is a medium-severity cross-site scripting vulnerability in Unknown SVG Uploads Support, published on 15 May 2025. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

The SVG Uploads Support WordPress plugin through 2.1.1 does not sanitize uploaded SVG files, which could allow users with a role as low as Author to upload a malicious SVG containing XSS payloads.

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

## Which versions are affected by CVE-2023-7086?

It affects 1 product.


Products: Ablyperu Svg Uploads Support.

## How do I fix CVE-2023-7086?

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

## Is CVE-2023-7086 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-7086 and fix it if it is affected.

What it is: CVE-2023-7086 is a medium-severity cross-site scripting vulnerability in Unknown SVG Uploads Support, published on 15 May 2025. Any signed-in user can exploit it over the network, 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-2023-7086 exists.

Affected product: Unknown SVG Uploads Support. 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-2023-7086/ (Markdown: https://insights.sbomify.com/CVE-2023-7086/index.md)
```

## Sources

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

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