# CVE-2022-44590: WordPress Simple Video Embedder plugin <= 2.2 - Auth. Stored Cross-Site Scripting (XSS) vulnerability

> Authenticated contributors can inject malicious scripts via stored XSS in the Simple Video Embedder plugin, potentially compromising user sessions.

- **Severity:** Medium 5.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:** 9 Nov 2022
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-x6f3-mx3x-9q4m

## What is CVE-2022-44590?

CVE-2022-44590 is a medium-severity cross-site scripting vulnerability in James Lao Simple Video Embedder (WordPress plugin), published on 9 Nov 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Auth. (contributor+) Stored Cross-Site Scripting (XSS) vulnerability in James Lao's Simple Video Embedder plugin <= 2.2 on WordPress.

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

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

It affects 1 product.


Products: Simple Video Embedder Project Simple Video Embedder.

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

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

## Is CVE-2022-44590 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-44590 is a medium-severity cross-site scripting vulnerability in James Lao Simple Video Embedder (WordPress plugin), published on 9 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-44590 in the wild and no public exploit code.

Affected product: James Lao Simple Video Embedder (WordPress plugin). 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-44590/ (Markdown: https://insights.sbomify.com/CVE-2022-44590/index.md)
```

## Sources

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

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