Stored script execution via unsanitized Task Name
Published Feb 14, 2024 · Updated Aug 1, 2024
Stored XSS in Task Manager App 1.0 allows remote attackers to execute arbitrary browser scripts through a crafted Task Name. Task.php accepts the Task Name value without adequate sanitization, so submitted HTML and SVG event handlers execute in the application origin. A victim must view the affected task content; execution occurs in that browser session and can expose cookie-based authentication data or alter page actions.
Summary
What happened
Stored XSS in Task Manager App 1.0 allows remote attackers to execute arbitrary browser scripts through a crafted Task Name. Task.php accepts the Task Name value without adequate sanitization, so submitted HTML and SVG event handlers execute in the application origin. A victim must view the affected task content; execution occurs in that browser session and can expose cookie-based authentication data or alter page actions.
The record
- CVE
- CVE-2024-25219
- Published
- Feb 14, 2024
- Updated
- Aug 1, 2024
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1539
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 14, 2024CVE publishedPublication date reported by the CVE source.
- Aug 1, 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
- Task Manager App - Cross-Site-Scripting - 2proof 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