Stored XSS via unfiltered file metadata
Published Jul 23, 2021 · Updated Aug 3, 2024
Stored XSS in Omeka Classic before 2.8 allows remote authenticated users to inject script through file metadata fields. The admin/files/edit form saves posted Elements metadata without passing it through Omeka's HTML purifier when HTML is enabled. Contributor, administrator, or superuser access is required to store the payload, which executes in another user's browser when a page containing the file is viewed.
Summary
What happened
Stored XSS in Omeka Classic before 2.8 allows remote authenticated users to inject script through file metadata fields. The admin/files/edit form saves posted Elements metadata without passing it through Omeka's HTML purifier when HTML is enabled. Contributor, administrator, or superuser access is required to store the payload, which executes in another user's browser when a page containing the file is viewed.
The record
- CVE
- CVE-2021-26799
- Published
- Jul 23, 2021
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 23, 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
- Stored XSS reproduction steps for admin/files/editproof 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