Stored XSS via unescaped document type labels
Published Aug 4, 2021 · Updated Aug 3, 2024
Stored XSS in the Liferay Document Library module allows remote attackers to inject arbitrary script through a document type name. MenuItemProvider._getFileEntryTypeMenuItem passes the label directly to urlMenuItem.setLabel without HTML escaping. Execution occurs when a user opens the affected add-document menu, allowing the script to run in that user's browser context.
Summary
What happened
Stored XSS in the Liferay Document Library module allows remote attackers to inject arbitrary script through a document type name. MenuItemProvider._getFileEntryTypeMenuItem passes the label directly to urlMenuItem.setLabel without HTML escaping. Execution occurs when a user opens the affected add-document menu, allowing the script to run in that user's browser context.
The record
- CVE
- CVE-2021-33337
- Published
- Aug 4, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1204
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 4, 2021CVE publishedPublication date reported by the CVE source.
- Aug 3, 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