# CVE-2022-1964: Easy SVG Support < 3.3.0 - Author+ Stored Cross Site Scripting via SVG

> An attacker with Author role can upload malicious SVG files to execute arbitrary scripts in the context of other users.

- **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:** 27 Jun 2022
- **Updated:** 3 Aug 2024
- **Also known as:** GHSA-f6vc-649h-9c88

## What is CVE-2022-1964?

CVE-2022-1964 is a medium-severity cross-site scripting vulnerability in Unknown Easy SVG Support, published on 27 Jun 2022. 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 Easy SVG Support WordPress plugin before 3.3.0 does not sanitise 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-2022-1964?

It affects 1 product.


Products: Easy Svg Support Project Easy Svg Support.

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

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

## Is CVE-2022-1964 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-1964 is a medium-severity cross-site scripting vulnerability in Unknown Easy SVG Support, published on 27 Jun 2022. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-1964 in the wild and no public exploit code.

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

## Sources

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

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