Script execution via unsanitized persistent report name
Published Feb 5, 2024 · Updated Jul 9, 2026
Stored XSS in Stimulsoft Dashboard.JS before 2024.1.2 allows remote attackers to execute script through a crafted ReportName value. The report definition preserves ReportName without sanitization and renders it in the designer's Properties search, where event-handler markup executes. Exploitation requires a user to load the crafted report and expand the search interface; the resulting script runs in the victim's browser context.
Summary
What happened
Stored XSS in Stimulsoft Dashboard.JS before 2024.1.2 allows remote attackers to execute script through a crafted ReportName value. The report definition preserves ReportName without sanitization and renders it in the designer's Properties search, where event-handler markup executes. Exploitation requires a user to load the crafted report and expand the search interface; the resulting script runs in the victim's browser context.
The record
- CVE
- CVE-2024-24397
- Published
- Feb 5, 2024
- Updated
- Jul 9, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 5, 2024CVE publishedPublication date reported by the CVE source.
- Jul 9, 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?
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 ReportName 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