Stored XSS via unsanitized list field saves
Published Jul 16, 2026 · Updated Jul 16, 2026
Stored XSS in Content Folder Kirby before 4.9.1 and 5.0.0 through 5.4.0 allows remote authenticated users to execute JavaScript. The server-side save path accepts list field HTML sent directly to the API without applying the sanitization enforced by the Panel, so persistent markup reaches frontend templates. Exploitation requires Panel update permission for a list field or list block and affects visitors or logged-in users who browse the resulting frontend page.
Summary
What happened
Stored XSS in Content Folder Kirby before 4.9.1 and 5.0.0 through 5.4.0 allows remote authenticated users to execute JavaScript. The server-side save path accepts list field HTML sent directly to the API without applying the sanitization enforced by the Panel, so persistent markup reaches frontend templates. Exploitation requires Panel update permission for a list field or list block and affects visitors or logged-in users who browse the resulting frontend page.
The record
- CVE
- CVE-2026-44175
- Published
- Jul 16, 2026
- Updated
- Jul 16, 2026
- Vendor
- Content Folder
- Product
- Kirby
- Classifications
- CWE-79, T1189
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Jul 16, 2026CVE publishedPublication date reported by the CVE source.
- Jul 16, 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=< 4.9.1
- Affected versionversion=>= 5.0.0, < 5.4.1
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
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