Stored XSS via unsanitized filter names
Published Jan 20, 2026 · Updated Jan 20, 2026
Stored XSS in The Starware WorklogPRO - Jira Timesheets before 4.24.2 allows remote authenticated users to execute script via filter names. The custom timesheet dialog renders a saved filter name in its dropdown without output encoding, causing embedded HTML or JavaScript to execute in the browser. The vendor reproduction requires authentication to store the payload and user interaction to open the affected filter interface; execution remains confined to the browsing context.
Summary
What happened
Stored XSS in The Starware WorklogPRO - Jira Timesheets before 4.24.2 allows remote authenticated users to execute script via filter names. The custom timesheet dialog renders a saved filter name in its dropdown without output encoding, causing embedded HTML or JavaScript to execute in the browser. The vendor reproduction requires authentication to store the payload and user interaction to open the affected filter interface; execution remains confined to the browsing context.
The record
- CVE
- CVE-2025-67824
- Published
- Jan 20, 2026
- Updated
- Jan 20, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jan 20, 2026CVE publishedPublication date reported by the CVE source.
- Jan 20, 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.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
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
- Vendor stored-XSS reproduction stepsproof 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