# CVE-2024-1647: pyhtml2pdf 0.0.6 - Local File Read via Server Side XSS

> An attacker can read arbitrary local files by injecting malicious HTML into the pyhtml2pdf library due to lack of input validation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 19 Feb 2024
- **Updated:** 3 Dec 2025
- **Also known as:** GHSA-p3rv-qj56-2fqx, PYSEC-2024-301

## What is CVE-2024-1647?

CVE-2024-1647 is a high-severity cross-site scripting vulnerability in pyhtml2pdf, published on 19 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Pyhtml2pdf version 0.0.6 allows an external attacker to remotely obtain

arbitrary local files. This is possible because the application does not

validate the HTML content entered by the user.

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

## Which versions are affected by CVE-2024-1647?

3 open source packages ship an affected version, including pyhtml2pdf. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `pyhtml2pdf` | PyPI | All versions to 0.0.6 | None |
| `pyhtml2pdf` | PyPI | All versions to 0.0.6 | None |
| `pyhtml2pdf` | PyPI | All versions to 0.0.6 | None |

Products: Kumaf Pyhtml2pdf.

## How do I fix CVE-2024-1647?

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

## Is CVE-2024-1647 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1647 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-1647 and fix it if it is affected.

What it is: CVE-2024-1647 is a high-severity cross-site scripting vulnerability in pyhtml2pdf, published on 19 Feb 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-1647 exists.

Affected packages and fixed versions:
- pyhtml2pdf (PyPI): affected all versions up to 0.0.6; no fix listed
- pyhtml2pdf (PyPI): affected all versions up to 0.0.6; no fix listed
- pyhtml2pdf (PyPI): affected all versions up to 0.0.6; 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-2024-1647/ (Markdown: https://insights.sbomify.com/CVE-2024-1647/index.md)
```

## Sources

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

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