# CVE-2023-3374: Privilege Escalation in Bookreen


- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 5 Sep 2023
- **Updated:** 22 May 2026
- **Also known as:** GHSA-67f9-wf2w-q22m

## What is CVE-2023-3374?

CVE-2023-3374 is a critical vulnerability in Unisign Bookreen, published on 5 Sep 2023. 

### Official description

Incomplete List of Disallowed Inputs vulnerability in Unisign Bookreen allows Privilege Escalation.

This issue affects Bookreen: before 3.0.0.

Weakness: CWE-184 (Incomplete List of Disallowed Inputs)

## Which versions are affected by CVE-2023-3374?

It affects 1 product.


Products: Bookreen Bookreen.

## How do I fix CVE-2023-3374?

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

## Is CVE-2023-3374 being exploited?

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

## Other vulnerabilities in Unisign Bookreen

- [CVE-2023-3375](https://insights.sbomify.com/CVE-2023-3375/): Unrestricted File Upload in Bookreen (high 7.2)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-3374 and fix it if it is affected.

What it is: CVE-2023-3374 is a critical vulnerability in Unisign Bookreen, published on 5 Sep 2023. 
Exploitation: There is no known exploitation of CVE-2023-3374 in the wild and no public exploit code.

Affected product: Unisign Bookreen. 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-2023-3374/ (Markdown: https://insights.sbomify.com/CVE-2023-3374/index.md)
```

## Sources

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

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