Arbitrary file write via unsanitized export paths
Published Nov 17, 2025 · Updated Nov 18, 2025
Path traversal in PDFPatcher before 1.1.3.4663 allows local users to write exported images outside the selected output directory. FileHelper.cs accepts raw traversal segments in an image-export destination and uses the uncanonicalized path for filesystem writes. Exploitation requires local use of the image-export interface, and resulting writes remain limited to locations permitted to the PDFPatcher process.
Summary
What happened
Path traversal in PDFPatcher before 1.1.3.4663 allows local users to write exported images outside the selected output directory. FileHelper.cs accepts raw traversal segments in an image-export destination and uses the uncanonicalized path for filesystem writes. Exploitation requires local use of the image-export interface, and resulting writes remain limited to locations permitted to the PDFPatcher process.
The record
- CVE
- CVE-2025-63918
- Published
- Nov 17, 2025
- Updated
- Nov 18, 2025
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-22
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Nov 17, 2025CVE publishedPublication date reported by the CVE source.
- Nov 18, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- PDFPatcher image-export directory traversal proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo