Stored script execution via unescaped uploaded filenames
Published Mar 26, 2026 · Updated Mar 26, 2026
Stored XSS in Uploady before 3.1.2 allows remote authenticated users to execute JavaScript in another user's browser via a crafted filename. The upload workflow stores the original filename, and file-list or file-details rendering treats its unescaped HTML characters as markup instead of text. A low-privileged uploader must plant the filename and another user must view it; the script runs in the application's origin and can read session data or act as that viewer.
Summary
What happened
Stored XSS in Uploady before 3.1.2 allows remote authenticated users to execute JavaScript in another user's browser via a crafted filename. The upload workflow stores the original filename, and file-list or file-details rendering treats its unescaped HTML characters as markup instead of text. A low-privileged uploader must plant the filename and another user must view it; the script runs in the application's origin and can read session data or act as that viewer.
The record
- CVE
- CVE-2026-33653
- Published
- Mar 26, 2026
- Updated
- Mar 26, 2026
- Vendor
- farisc0de
- Product
- Uploady
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 26, 2026CVE publishedPublication date reported by the CVE source.
- Mar 26, 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=< 3.1.2
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
- Upstream malicious-filename stored-XSS 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