Reflected XSS via unsanitized uploaded filenames
Published Apr 17, 2026 · Updated Apr 17, 2026
Reflected XSS in Stirling PDF before 2.0.0 allows remote attackers to execute JavaScript by inducing a user to upload a crafted file. Upload interfaces place the user-controlled filename into HTML with innerHTML without encoding or sanitizing special characters. Exploitation requires the targeted user to upload the attacker-crafted file; the script then runs only in that user’s active browser session and can read browser-visible data.
Summary
What happened
Reflected XSS in Stirling PDF before 2.0.0 allows remote attackers to execute JavaScript by inducing a user to upload a crafted file. Upload interfaces place the user-controlled filename into HTML with innerHTML without encoding or sanitizing special characters. Exploitation requires the targeted user to upload the attacker-crafted file; the script then runs only in that user’s active browser session and can read browser-visible data.
The record
- CVE
- CVE-2026-33436
- Published
- Apr 17, 2026
- Updated
- Apr 17, 2026
- Vendor
- Stirling PDF
- Product
- Stirling PDF
- Classifications
- CWE-116, CWE-20, CWE-79, T1204.002
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 17, 2026CVE publishedPublication date reported by the CVE source.
- Apr 17, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=< 2.0.0
What conditions does exploitation require?
What is affected?
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
- GHSA-q5j3-4m5w-wp75 filename 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