Stored XSS via unsanitized SVG uploads
Published Nov 21, 2024 · Updated Apr 8, 2026
Stored XSS in LightSpeed WordPress Development LSX Tour Operator 1.4.9 and earlier allows remote authenticated users to run scripts via SVG uploads. The SVG upload path accepts attacker-controlled script content without sufficient input sanitization, and the file is served without output escaping. Author-level access is required to upload the file; the script executes in the browser of anyone who later opens the stored SVG, exposing that user’s session context to script actions.
Summary
What happened
Stored XSS in LightSpeed WordPress Development LSX Tour Operator 1.4.9 and earlier allows remote authenticated users to run scripts via SVG uploads. The SVG upload path accepts attacker-controlled script content without sufficient input sanitization, and the file is served without output escaping. Author-level access is required to upload the file; the script executes in the browser of anyone who later opens the stored SVG, exposing that user’s session context to script actions.
The record
- CVE
- CVE-2024-9851
- Published
- Nov 21, 2024
- Updated
- Apr 8, 2026
- Vendor
- LightSpeed WordPress Development
- Product
- LSX Tour Operator
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Nov 21, 2024CVE publishedPublication date reported by the CVE source.
- Apr 8, 2026Record 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=1.4.9
What conditions does exploitation require?
What is affected?
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