CVE-2026-61823 code16 Sharp vulnerable to stored XSS via iframe srcdoc Attribute
Authenticated users can inject JavaScript via iframe srcdoc in the rich-text editor, leading to session hijacking and privilege escalation for other users.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-61823?
CVE-2026-61823 is a high-severity cross-site scripting vulnerability in code16 sharp, published on 24 Sep 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
code16 Sharp is a Laravel-based framework for building content-management and administrative interfaces. Versions before 9.22.5 contain a stored cross-site scripting vulnerability in the rich-text editor because the HTML sanitizer permits the `srcdoc` attribute on iframe elements. Although markup inside `srcdoc` is HTML-encoded during sanitization, browsers decode attribute entities before interpreting the iframe document, allowing an authenticated user with permission to edit an Editor field to store executable JavaScript that runs when another user views the content. Successful exploitation can result in session hijacking, unauthorized actions, account takeover, privilege escalation, or disclosure of administrative data. Version 9.22.5 patches the vulnerability by removing `srcdoc` from the permitted iframe attributes. As a workaround, applications that cannot upgrade should manually sanitize all Editor field content and remove every iframe `srcdoc` attribute before storing or rendering it.
Weakness: CWE-79
Which versions are affected by CVE-2026-61823?
2 open source packages ship an affected version, including code16/sharp.
| Package | Affected | Fixed in |
|---|---|---|
code16/sharp Packagist | All versions | 9.22.5 |
code16/sharp Packagist | All versions | 9.22.5 |
How do I fix CVE-2026-61823?
Upgrade code16/sharp to 9.22.5 or later.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-61823 being exploited?
There is no known exploitation of CVE-2026-61823 in the wild and no public exploit code.
Sources
Also known as GHSA-qxg3-46rw-79j8.