# CVE-2022-4022: Cross-site scripting in SVG Support

> Authenticated attackers can upload malicious SVG files to execute JavaScript in browsers, potentially leading to account takeover.

- **Severity:** Medium 6.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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:** Not needed
- **Fix available:** No
- **Published:** 16 Nov 2022
- **Updated:** 7 Feb 2025
- **Also known as:** GHSA-mwcq-5rpw-7p42

## What is CVE-2022-4022?

CVE-2022-4022 is a medium-severity cross-site scripting vulnerability in benbodhi SVG Support, published on 16 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The SVG Support plugin for WordPress defaults to insecure settings in version 2.5 and 2.5.1. SVG files containing malicious javascript are not sanitized. While version 2.5 adds the ability to sanitize image as they are uploaded, the plugin defaults to disable sanitization and does not restrict SVG upload to only administrators. This allows authenticated attackers, with author-level privileges and higher, to upload malicious SVG files that can be embedded in posts and pages by higher privileged users. Additionally, the embedded JavaScript is also triggered on visiting the image URL, which allows an attacker to execute malicious code in browsers visiting that URL.

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

## Which versions are affected by CVE-2022-4022?

It affects 1 product.


Products: Benbodhi Svg Support.

## How do I fix CVE-2022-4022?

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

## Is CVE-2022-4022 being exploited?

There is no known exploitation of CVE-2022-4022 in the wild and no public exploit code.

## Other vulnerabilities in benbodhi SVG Support

- [CVE-2024-10222](https://insights.sbomify.com/CVE-2024-10222/): SVG Support <= 2.5.10 - Authenticated (Author+) Stored Cross-Site Scripting via SVG File Upload (medium 6.4)
- [CVE-2022-1755](https://insights.sbomify.com/CVE-2022-1755/): SVG Support < 2.5 - Author+ Stored Cross-Site Scripting (medium 5.4)
- [CVE-2021-24686](https://insights.sbomify.com/CVE-2021-24686/): SVG Support < 2.3.20 - Admin+ Stored Cross-Site Scripting (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-4022 and fix it if it is affected.

What it is: CVE-2022-4022 is a medium-severity cross-site scripting vulnerability in benbodhi SVG Support, published on 16 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-4022 in the wild and no public exploit code.

Affected product: benbodhi SVG 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-2022-4022/ (Markdown: https://insights.sbomify.com/CVE-2022-4022/index.md)
```

## Sources

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

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