Stored XSS via ticket content rendering
Published Mar 5, 2020 · Updated Aug 4, 2024
Stored XSS in Zammad 1.0.x through 3.2.0 allows remote authenticated users to execute JavaScript in another user's browser via tickets. The Ticket functionality stores attacker-supplied JavaScript and renders it in ticket views and Toolbar entries without effective neutralization. Low-privileged access is sufficient; execution requires another user to open the ticket or keep it in the Toolbar, exposing that user's browser session to script-driven actions.
Summary
What happened
Stored XSS in Zammad 1.0.x through 3.2.0 allows remote authenticated users to execute JavaScript in another user's browser via tickets. The Ticket functionality stores attacker-supplied JavaScript and renders it in ticket views and Toolbar entries without effective neutralization. Low-privileged access is sufficient; execution requires another user to open the ticket or keep it in the Toolbar, exposing that user's browser session to script-driven actions.
The record
- CVE
- CVE-2020-10099
- Published
- Mar 5, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 5, 2020CVE publishedPublication date reported by the CVE source.
- Aug 4, 2024Record 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.
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
No public exploit references are available in this record.
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