# CVE-2022-37721: PyroCMS vulnerable to stored Cross Site Scripting

> A stored XSS vulnerability in PyroCMS allows low-privileged users to inject scripts, potentially leading to admin account takeover or privilege escalation.

- **Severity:** Critical 9.0 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/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:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Nov 2022
- **Updated:** 9 Jul 2026
- **Also known as:** GHSA-cm7f-hf2g-ghrp

## What is CVE-2022-37721?

CVE-2022-37721 is a critical cross-site scripting vulnerability in n/a, published on 25 Nov 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

PyroCMS 3.9 is vulnerable to a stored Cross Site Scripting (XSS_ when a low privileged user such as an author, injects a crafted html and javascript payload in a blog post, leading to full admin account takeover or privilege escalation.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pyrocms/pyrocms` | Packagist | All versions to 3.9.1 | None |
| `pyrocms/pyrocms` | Packagist | All versions to 3.9.1 | None |

Products: Pyrocms Pyrocms.

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

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

## Is CVE-2022-37721 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2023-29689](https://insights.sbomify.com/CVE-2023-29689/): PyroCMS remote code execution vulnerability (critical 9.8)
- [CVE-2020-25263](https://insights.sbomify.com/CVE-2020-25263/): PyroCMS Vulnerable to CSRF (high 7.1)
- [CVE-2022-35118](https://insights.sbomify.com/CVE-2022-35118/): Cross-site scripting in n/a (medium 6.1)
- [CVE-2024-58297](https://insights.sbomify.com/CVE-2024-58297/): PyroCMS v3.0.1 Stored Cross-Site Scripting via Admin Redirects (medium 5.3)
- [CVE-2020-25262](https://insights.sbomify.com/CVE-2020-25262/): PyroCMS Vulnerable to CSRF (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-37721 is a critical cross-site scripting vulnerability in n/a, published on 25 Nov 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-37721 in the wild and no public exploit code.

Affected packages and fixed versions:
- pyrocms/pyrocms (Packagist): affected all versions up to 3.9.1; no fix listed
- pyrocms/pyrocms (Packagist): affected all versions up to 3.9.1; 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-37721/ (Markdown: https://insights.sbomify.com/CVE-2022-37721/index.md)
```

## Sources

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

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