Stored XSS via unescaped checklist names
Published Jun 26, 2024 · Updated Aug 1, 2024
Stored XSS in Jonas Breuer Frontend Checklist 2.3.2 and earlier allows remote authenticated users to execute scripts via checklist names. The checklist creation page stores the name field without adequate sanitization, and the admin listing page renders it without output escaping. Administrator privileges and a victim who opens the checklist listing are required; the stored script then runs in that browser even when unfiltered_html is disabled.
Summary
What happened
Stored XSS in Jonas Breuer Frontend Checklist 2.3.2 and earlier allows remote authenticated users to execute scripts via checklist names. The checklist creation page stores the name field without adequate sanitization, and the admin listing page renders it without output escaping. Administrator privileges and a victim who opens the checklist listing are required; the stored script then runs in that browser even when unfiltered_html is disabled.
The record
- CVE
- CVE-2024-4957
- Published
- Jun 26, 2024
- Updated
- Aug 1, 2024
- Vendor
- Jonas Breuer
- Product
- Frontend Checklist
- Classifications
- CWE-79, T1059.007
- Attack vector
- network
- Privileges
- admin
Timeline
How it unfolded
- Jun 26, 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?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=0 <=2.3.2
What conditions does exploitation require?
What is affected?
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
- WPScan checklist-name stored XSS 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