Stored XSS via unsanitized comment rendering
Published Aug 26, 2026 · Updated Aug 27, 2026
Stored XSS in Penpot file comments before 2.15.3 allows remote authenticated users to execute script in collaborators' browsers. The backend accepts comment content with only a length check, and comments.cljs passes the stored text to dom/set-html!, which assigns it to innerHTML without sanitization. Any team member who can comment triggers execution when another collaborator opens the comments panel, enabling session theft and actions with the victim's access.
Summary
What happened
Stored XSS in Penpot file comments before 2.15.3 allows remote authenticated users to execute script in collaborators' browsers. The backend accepts comment content with only a length check, and comments.cljs passes the stored text to dom/set-html!, which assigns it to innerHTML without sanitization. Any team member who can comment triggers execution when another collaborator opens the comments panel, enabling session theft and actions with the victim's access.
The record
- CVE
- CVE-2026-47665
- Published
- Aug 26, 2026
- Updated
- Aug 27, 2026
- Vendor
- Penpot
- Product
- Penpot
- Classifications
- CWE-79, T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Aug 26, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 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=< 2.15.3
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
- GitHub advisory stored-comment 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