Authenticated browser code execution via unsanitized report comments
Published Feb 11, 2022 · Updated Sep 16, 2024
Stored XSS in WOCU-Monitoring before 48.2 allows remote authenticated users to execute JavaScript through report comments. The Reports module passes saved rich-text attributes to TinyMCE setContent without adequate validation or restrictive server-side sanitization. An account able to view and edit reports is required, and a report viewer must open the stored comment for code to run in that viewer's browser.
Summary
What happened
Stored XSS in WOCU-Monitoring before 48.2 allows remote authenticated users to execute JavaScript through report comments. The Reports module passes saved rich-text attributes to TinyMCE setContent without adequate validation or restrictive server-side sanitization. An account able to view and edit reports is required, and a report viewer must open the stored comment for code to run in that viewer's browser.
The record
- CVE
- CVE-2021-4035
- Published
- Feb 11, 2022
- Updated
- Sep 16, 2024
- Vendor
- A3Sec
- Product
- WOCU-Monitoring
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Feb 11, 2022CVE publishedPublication date reported by the CVE source.
- Sep 16, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0.27 <48.2
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
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