# CVE-2022-0877: Cross-site Scripting (XSS) - Stored in bookstackapp/bookstack

> Attackers can inject malicious scripts into BookStack documentation pages, potentially stealing user sessions or executing code in victim browsers.

- **Severity:** High 7.6 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:L/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:** Yes
- **Published:** 8 Mar 2022
- **Updated:** 2 Aug 2024
- **Also known as:** GHSA-5rcc-6cmj-7728

## What is CVE-2022-0877?

CVE-2022-0877 is a high-severity cross-site scripting vulnerability in bookstackapp/bookstack, published on 8 Mar 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

Cross-site Scripting (XSS) - Stored in GitHub repository bookstackapp/bookstack prior to v22.02.3.

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

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

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `ssddanbrown/bookstack` | Packagist | All versions | 22.02.3 |
| `ssddanbrown/bookstack` | Packagist | All versions | 22.02.3 |

Products: Bookstackapp Bookstack.

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

Upgrade ssddanbrown/bookstack to 22.02.3 or later.

## Is CVE-2022-0877 being exploited?

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

## Other vulnerabilities in bookstackapp/bookstack

- [CVE-2020-5256](https://insights.sbomify.com/CVE-2020-5256/): Remote Code Execution Through Image Uploads in BookStack (high 7.9)
- [CVE-2020-26210](https://insights.sbomify.com/CVE-2020-26210/): Cross-Site Scripting in BookStack (high 7.7)
- [CVE-2020-26211](https://insights.sbomify.com/CVE-2020-26211/): Cross-Site Scripting in BookStack (high 7.7)
- [CVE-2021-3915](https://insights.sbomify.com/CVE-2021-3915/): Unrestricted Upload of File with Dangerous Type in bookstackapp/bookstack (high 7.6)
- [CVE-2023-6199](https://insights.sbomify.com/CVE-2023-6199/): Book Stack v23.10.2 - LFR via Blind SSRF (medium 6.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-0877 is a high-severity cross-site scripting vulnerability in bookstackapp/bookstack, published on 8 Mar 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-0877 in the wild and no public exploit code.

Affected packages and fixed versions:
- ssddanbrown/bookstack (Packagist): affected all versions; fixed in 22.02.3
- ssddanbrown/bookstack (Packagist): affected all versions; fixed in 22.02.3

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

## Sources

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

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