CVE-2026-61825: code16/sharp has a stored XSS via data-html-content Sanitizer Bypass

Published Sep 24, 2026
·
Updated

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 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. The vendor identifies version 9.22.5 as patched; applications that intentionally enable SharpFormEditorField::RAWHTML must continue to sanitize editor content themselves. As a workaround, applications should sanitize all editor content before storing or rendering it, for example with Symfony HtmlSanitizer, and disable RAWHTML functionality where it is not required.

Affected Software

1 affected component
packagist/code16/sharp<9.22.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade code16/sharp to a version that resolves this vulnerability.

    Fixed in 9.22.5
  2. Configuration

    Disable RAW_HTML functionality where it is not required.

    code16 Sharp SharpFormEditorField::RAW_HTML = disabled
  3. Compensating control

    Sanitize all editor content before storing or rendering it, for example with Symfony HtmlSanitizer; applications that intentionally enable SharpFormEditorField::RAW_HTML must continue sanitizing editor content themselves.

Event History

Sep 24, 2026
CVE Published
via MITRE·06:27 PM
Data Sourced
via MITRE·06:27 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·07:17 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Who can exploit this issue, and who is at risk from the stored payload?

An attacker needs privileges to submit content through the affected SharpEditorFormField and must persuade or wait for another user to view the stored content. The impact can extend to the viewing user's browser, including confidentiality and integrity effects.

2

Are all deployments protected by upgrading to version 9.22.5?

Version 9.22.5 is identified as patched. However, applications that intentionally enable SharpFormEditorField::RAW_HTML must continue to sanitize editor content themselves.

3

What can be done if the update cannot be applied immediately?

Sanitize all editor content before it is stored or rendered, such as by using Symfony HtmlSanitizer. Disable RAW_HTML where it is not required.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203