# CVE-2022-50897: mPDF 7.0 - Local File Inclusion

> Attackers can read arbitrary system files by manipulating annotation file parameters in the mPDF library.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Jan 2026
- **Updated:** 5 Mar 2026
- **Also known as:** GHSA-r9c5-x9r9-f4w3

## What is CVE-2022-50897?

CVE-2022-50897 is a high-severity path traversal vulnerability in mPDF, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

mPDF 7.0 contains a local file inclusion vulnerability that allows attackers to read arbitrary system files by manipulating annotation file parameters. Attackers can generate URL-encoded or base64 payloads to include local files through crafted annotation content with file path specifications.

Weakness: CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program)

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

It affects 1 product.


Products: Mpdf Project Mpdf.

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

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

## Is CVE-2022-50897 being exploited?

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

## Other vulnerabilities in mPDF

- [CVE-2018-19047](https://insights.sbomify.com/CVE-2018-19047/): Server-side request forgery in n/a (critical 10.0)
- [CVE-2019-1000005](https://insights.sbomify.com/CVE-2019-1000005/): mPDF Unsafe Deserialization (high 8.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-50897 is a high-severity path traversal vulnerability in mPDF, published on 13 Jan 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-50897 in the wild and no public exploit code.

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

## Sources

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

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