Browser script execution via unsanitized plist data
Published Mar 12, 2022 · Updated Aug 3, 2024
Reflected XSS in Alist 2.0.10 through 2.1.0 allows remote attackers to execute script in a user's browser via a crafted plist URL. The Plist handler base64-decodes the route data and inserts the resulting URL and derived name into XML with fmt.Sprintf without output encoding. Exploitation requires a user to open the crafted endpoint; injected script runs in the Alist origin and can read or alter browser-accessible data.
Summary
What happened
Reflected XSS in Alist 2.0.10 through 2.1.0 allows remote attackers to execute script in a user's browser via a crafted plist URL. The Plist handler base64-decodes the route data and inserts the resulting URL and derived name into XML with fmt.Sprintf without output encoding. Exploitation requires a user to open the crafted endpoint; injected script runs in the Alist origin and can read or alter browser-accessible data.
The record
- CVE
- CVE-2022-26533
- Published
- Mar 12, 2022
- Updated
- Aug 3, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 12, 2022CVE 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
- Alist plist-route XSS 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