Stored XSS via executable SVG upload
Published Dec 14, 2021 · Updated Aug 4, 2024
Stored XSS in AbanteCart before 1.3.2 allows remote authenticated users to execute JavaScript by uploading a malicious SVG file. The file-upload path accepts SVG documents containing script and serves them from a location where a browser executes the embedded payload when opened. Low-privileged access with file-upload permission is required, and a victim must visit the stored SVG; the script then runs in that victim's browser context.
Summary
What happened
Stored XSS in AbanteCart before 1.3.2 allows remote authenticated users to execute JavaScript by uploading a malicious SVG file. The file-upload path accepts SVG documents containing script and serves them from a location where a browser executes the embedded payload when opened. Low-privileged access with file-upload permission is required, and a victim must visit the stored SVG; the script then runs in that victim's browser context.
The record
- CVE
- CVE-2021-42051
- Published
- Dec 14, 2021
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Dec 14, 2021CVE 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
- SEC Consult malicious SVG 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