# CVE-2025-63917: XML external entity in n/a

> Attackers can exploit XML bookmark import to read files, exfiltrate data, or cause denial of service via XXE in PDFPatcher.

- **Severity:** High 7.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Nov 2025
- **Updated:** 17 Nov 2025
- **Also known as:** GHSA-59qf-vrm9-q977

## What is CVE-2025-63917?

CVE-2025-63917 is a high-severity vulnerability in n/a, published on 17 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

PDFPatcher thru 1.1.3.4663 executable's XML bookmark import functionality does not restrict XML external entity (XXE) references. The application uses .NET's XmlDocument class without disabling external entity resolution, enabling attackers to: Read arbitrary files from the victim's filesystem, exfiltrate sensitive data via out-of-band (OOB) HTTP requests, perform SSRF attacks against internal network resources, or cause a denial of service via entity expansion attacks.

Weakness: CWE-611 (Improper Restriction of XML External Entity Reference)

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

It affects 1 product.


Products: Cnblogs Pdfpatcher.

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

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

## Is CVE-2025-63917 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-63918](https://insights.sbomify.com/CVE-2025-63918/): Path traversal in n/a (medium 6.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-63917 is a high-severity vulnerability in n/a, published on 17 Nov 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-63917 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-63917/ (Markdown: https://insights.sbomify.com/CVE-2025-63917/index.md)
```

## Sources

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

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