Stored XSS via unescaped attachment filenames
Published Sep 8, 2022 · Updated Apr 22, 2025
Stored XSS in the attachment-history view in XWiki Platform allows remote authenticated users to execute JavaScript in viewers' browsers. The viewattachrev.vm template passes the attachment filename directly to localization output and an image alt attribute without XML escaping. An account able to attach a file with a crafted name must first store the payload, and another user must open that attachment's history; the script then runs with that viewer's web-session access.
Summary
What happened
Stored XSS in the attachment-history view in XWiki Platform allows remote authenticated users to execute JavaScript in viewers' browsers. The viewattachrev.vm template passes the attachment filename directly to localization output and an image alt attribute without XML escaping. An account able to attach a file with a crafted name must first store the payload, and another user must open that attachment's history; the script then runs with that viewer's web-session access.
The record
- CVE
- CVE-2022-36094
- Published
- Sep 8, 2022
- Updated
- Apr 22, 2025
- Vendor
- CryptPad
- Product
- XWiki Platform
- Classifications
- CWE-79, CWE-80, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 8, 2022CVE publishedPublication date reported by the CVE source.
- Apr 22, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=>= 1.0, < 13.10.6
- Affected versionversion=>= 14.0, < 14.3-rc-1
What conditions does exploitation require?
What is affected?
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
- Crafted attachment 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