Stored XSS via content-unvalidated SVG logo upload
Published Jun 24, 2020 · Updated Aug 4, 2024
Stored XSS in Bludit 3.12.0 allows remote authenticated users to execute JavaScript in another user's browser through an SVG logo upload. The bl-kernel/ajax/logo-upload.php handler checks only the uploaded filename suffix and stores active SVG content without validating its contents. A logged-in user must upload the file, and a victim must view the stored logo for its embedded script and HTML to run in the Bludit origin.
Summary
What happened
Stored XSS in Bludit 3.12.0 allows remote authenticated users to execute JavaScript in another user's browser through an SVG logo upload. The bl-kernel/ajax/logo-upload.php handler checks only the uploaded filename suffix and stores active SVG content without validating its contents. A logged-in user must upload the file, and a victim must view the stored logo for its embedded script and HTML to run in the Bludit origin.
The record
- CVE
- CVE-2020-15006
- Published
- Jun 24, 2020
- Updated
- Aug 4, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jun 24, 2020CVE 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
- Stored SVG logo XSS proof of conceptproof of concept · unverified
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