# CVE-2022-0145: Cross-site Scripting (XSS) - Stored in forkcms/forkcms

> Stored Cross-Site Scripting in Fork CMS allows attackers to inject malicious scripts, potentially leading to session hijacking or code execution.

- **Severity:** Medium 6.8 (`CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Mar 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-qf2g-q4mc-w7rr

## What is CVE-2022-0145?

CVE-2022-0145 is a medium-severity cross-site scripting vulnerability in forkcms/forkcms, published on 24 Mar 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Cross-site Scripting (XSS) - Stored in GitHub repository forkcms/forkcms prior to 5.11.1.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `forkcms/forkcms` | Packagist | All versions | 5.11.1 |
| `forkcms/forkcms` | Packagist | All versions | 5.11.1 |

Products: Fork-Cms Fork Cms.

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

Upgrade forkcms/forkcms to 5.11.1 or later.

## Is CVE-2022-0145 being exploited?

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

## Other vulnerabilities in forkcms/forkcms

- [CVE-2019-15521](https://insights.sbomify.com/CVE-2019-15521/): Spoon Library as used in Fork CMS allows PHP object injection (critical 9.8)
- [CVE-2022-0153](https://insights.sbomify.com/CVE-2022-0153/): SQL Injection in forkcms/forkcms (critical 9.6)
- [CVE-2022-1064](https://insights.sbomify.com/CVE-2022-1064/): SQL injection through marking blog comments on bulk as spam in forkcms/forkcms (critical 9.0)
- [CVE-2021-28931](https://insights.sbomify.com/CVE-2021-28931/): Arbitrary file upload in Fork CMS (high 8.8)
- [CVE-2020-23264](https://insights.sbomify.com/CVE-2020-23264/): Cross-Site Request Forgery in forkcms (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0145 is a medium-severity cross-site scripting vulnerability in forkcms/forkcms, published on 24 Mar 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-0145 in the wild and no public exploit code.

Affected packages and fixed versions:
- forkcms/forkcms (Packagist): affected all versions; fixed in 5.11.1
- forkcms/forkcms (Packagist): affected all versions; fixed in 5.11.1

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

## Sources

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

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