CVE-2026-61823
HighCVSS 7.3Exploitation Probability (EPSS)
Low risk10th percentile - higher than 10% of all known CVEs
Summary
code16 Sharp, a Laravel-based framework for building content-management and administrative interfaces, prior to 9.22.5 contains 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. Version 9.22.5 removes srcdoc from permitted iframe attributes.
Risk Assessment
Successful exploitation can result in session hijacking, unauthorized actions, account takeover, privilege escalation, or disclosure of administrative data. The risk affects any user viewing the stored content.
Recommendation
Upgrade code16 Sharp to version 9.22.5 or later. If upgrading is not possible, manually sanitize all Editor field content and remove every iframe srcdoc attribute before storing or rendering it.
Other vulnerabilities in code16 Sharp
See all- CVE-2026-61825High
code16 Sharp, a Laravel-based framework for building content-management and administrative interfaces, prior to 9.22.5 contains a stored cross-site scripting vulnerability in SharpEditorFormField. Attacker-controlled content bearing the data-html-content attribute can bypass HTML sanitization and preserve executable markup, which may execute when another user views the stored content. Version 9.22.5 is identified as patched.
- CVE-2025-61457Medium
code16 Sharp v9.6.6 is vulnerable to Cross Site Scripting (XSS) src/Form/Fields/SharpFormUploadField.php.
Original NVD description (English source)
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.
Vulnerability data from NVD (NIST) · CISA KEV · EPSS