# CVE-2025-63918: Path traversal in n/a

> Attackers can upload arbitrary files to arbitrary locations due to lack of file path validation in PDFPatcher.

- **Severity:** Medium 6.2 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Nov 2025
- **Updated:** 18 Nov 2025
- **Also known as:** GHSA-h764-vg49-mhv9

## What is CVE-2025-63918?

CVE-2025-63918 is a medium-severity path traversal vulnerability in n/a, published on 17 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

PDFPatcher executable does not validate user-supplied file paths, allowing directory traversal attacks allowing attackers to upload arbitrary files to arbitrary locations.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-63918?

It affects 1 product.


Products: Cnblogs Pdfpatcher.

## How do I fix CVE-2025-63918?

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

## Is CVE-2025-63918 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-63917](https://insights.sbomify.com/CVE-2025-63917/): XML external entity in n/a (high 7.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-63918 and fix it if it is affected.

What it is: CVE-2025-63918 is a medium-severity path traversal vulnerability in n/a, published on 17 Nov 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63918 exists.

Affected product: n/a. 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-2025-63918/ (Markdown: https://insights.sbomify.com/CVE-2025-63918/index.md)
```

## Sources

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

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