# CVE-2022-32114: Strapi 4.1.12 Cross-site Scripting via crafted file

> Attackers can upload malicious PDFs to trigger XSS, though the vendor notes this requires specific permissions and public asset access.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`)
- **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:** 13 Jul 2022
- **Updated:** 13 Feb 2025
- **Also known as:** GHSA-4vm8-j95f-j6v5

## What is CVE-2022-32114?

CVE-2022-32114 is a high-severity vulnerability in n/a, published on 13 Jul 2022. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An unrestricted file upload vulnerability in the Add New Assets function of Strapi 4.1.12 allows attackers to conduct XSS attacks via a crafted PDF file. NOTE: the project documentation suggests that a user with the Media Library "Create (upload)" permission is supposed to be able to upload PDF files containing JavaScript, and that all files in a public assets folder are accessible to the outside world (unless the filename begins with a dot character). The administrator can choose to allow only image, video, and audio files (i.e., not PDF) if desired.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type)

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

2 open source packages ship an affected version, including @strapi/strapi. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `@strapi/strapi` | npm | All versions to 4.1.12 | None |
| `@strapi/strapi` | npm | All versions to 4.1.12 | None |

Products: Strapi Strapi.

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

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

## Is CVE-2022-32114 being exploited?

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

Public exploit code:

- An unrestricted file upload vulnerability in the Add New Assets function of Strapi v4.1.12 allows attackers to execute arbitrary code via a crafted file. (github_poc): https://github.com/bypazs/CVE-2022-32114

## Other vulnerabilities in n/a

- [CVE-2023-22894](https://insights.sbomify.com/CVE-2023-22894/): Strapi Cleartext Storage of Sensitive Information (high 7.2, exploited in the wild)
- [CVE-2023-22621](https://insights.sbomify.com/CVE-2023-22621/): Strapi plugins vulnerable to Server-Side Template Injection and Remote Code Execution in the Users-Permissions Plugin (critical 10.0)
- [CVE-2022-27263](https://insights.sbomify.com/CVE-2022-27263/): Unrestricted Upload of File with Dangerous Type in Strapi (critical 9.8)
- [CVE-2020-27664](https://insights.sbomify.com/CVE-2020-27664/): Authorization bypass in Strapi (critical 9.8)
- [CVE-2019-18818](https://insights.sbomify.com/CVE-2019-18818/): Strapi allows unauthenticated attacker to reset admin password without valid reset token (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-32114 is a high-severity vulnerability in n/a, published on 13 Jul 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-32114 in the wild and no public exploit code.

Affected packages and fixed versions:
- @strapi/strapi (npm): affected all versions up to 4.1.12; no fix listed
- @strapi/strapi (npm): affected all versions up to 4.1.12; no fix listed

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-32114/ (Markdown: https://insights.sbomify.com/CVE-2022-32114/index.md)
```

## Sources

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

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