# CVE-2022-3984: Flowplayer Video Player < 1.0.5 - Contributor+ Stored XSS

> Contributors can inject malicious scripts via shortcode attributes in the Flowplayer Video Player plugin, leading to stored XSS attacks.

- **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:** 19 Dec 2022
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-vc27-q7r5-rh9q

## What is CVE-2022-3984?

CVE-2022-3984 is a medium-severity cross-site scripting vulnerability in Unknown Flowplayer Video Player, published on 19 Dec 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 Flowplayer Video Player WordPress plugin before 1.0.5 does not validate and escape some of its shortcode attributes before outputting them back in the page, which could allow users with a role as low as contributor to perform Stored Cross-Site Scripting attacks

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

It affects 1 product.


Products: Wphowto Flowplayer Video Player.

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

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

## Is CVE-2022-3984 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-3984 is a medium-severity cross-site scripting vulnerability in Unknown Flowplayer Video Player, published on 19 Dec 2022. 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-2022-3984 exists.

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

## Sources

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

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