Stored XSS via data-html-content sanitizer bypass
Published Sep 24, 2026 · Updated Sep 24, 2026
Stored XSS in Code16 Sharp before 9.22.5 allows remote authenticated users to execute script when another user views crafted editor content. SharpEditorFormField preserves executable markup when attacker-controlled content bears the data-html-content attribute, allowing it to survive storage and render later. Exploitation requires permission to store editor content and another user to view it; RAW_HTML content remains intentionally unsanitized by design.
Summary
What happened
Stored XSS in Code16 Sharp before 9.22.5 allows remote authenticated users to execute script when another user views crafted editor content. SharpEditorFormField preserves executable markup when attacker-controlled content bears the data-html-content attribute, allowing it to survive storage and render later. Exploitation requires permission to store editor content and another user to view it; RAW_HTML content remains intentionally unsanitized by design.
The record
- CVE
- CVE-2026-61825
- Published
- Sep 24, 2026
- Updated
- Sep 24, 2026
- Vendor
- Code16
- Product
- Sharp
- Classifications
- T1203
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Sep 24, 2026CVE publishedPublication date reported by the CVE source.
- Sep 24, 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=< 9.22.5
What conditions does exploitation require?
What is affected?
Published CVSS scores
No CVSS assessment is available in this record.
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.
Activity data is delayed. The latest report is Sep 28, 2026.
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
Get started to see how Hinoki identifies affected software and validates exploitability in your environment.
Get started