GHSA-qxg3-46rw-79j8: XSS

Published Sep 25, 2026
·
Updated

Impact A Stored Cross-Site Scripting (XSS) vulnerability exists in the rich text editor due to improper sanitization of the srcdoc attribute on <iframe> elements.

While the underlying Symfony HtmlSanitizer correctly HTML-encodes special characters inside the attribute value (e.g., converting <script> to &lt;script&gt;), the HTML specification mandates that browsers automatically decode HTML entities inside attribute values before processing them. As a result, any encoded JavaScript inside a srcdoc attribute is evaluated and executed as live HTML/JS in the context of the iframe when the page is rendered.

An attacker with permissions to edit an Editor field can inject malicious scripts to target other users viewing the content. Potential impacts include:

- Session Hijacking (stealing admin session cookies via document.cookie) - Account Takeover & Privilege Escalation (e.g., a low-privileged editor triggering actions as an Administrator) - Admin panel data theft

Patches The vulnerability has been patched in version v9.22.5.

The fix explicitly removes srcdoc from the list of allowed iframe attributes in src/Utils/Sanitization/FormatsSanitizedValue.php.

Workarounds Users who cannot upgrade immediately can manually sanitize all content of editor fields to strip srcdoc attributes.

Affected Software

1 affected componentFixes available
composer/code16/sharp<9.22.5
9.22.5

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

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

    Fixed in 9.22.5
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in v9.22.5
  3. Compensating control

    Manually sanitize all content of editor fields to strip srcdoc attributes until upgrading.

Event History

Sep 25, 2026
Advisory Published
via GitHub·03:02 PM
Data Sourced
via GitHub·03:02 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

Who can exploit this issue?

An attacker needs permission to edit an Editor field. They can place malicious content that executes when another user views the affected content.

2

Which users are at risk when malicious content is rendered?

Other users who view the attacker-controlled Editor content may be targeted, including administrators. The stated impacts include session-cookie theft, actions performed with an administrator’s privileges, and admin-panel data theft.

3

What version contains the fix?

The issue is patched in v9.22.5. The fix removes the srcdoc attribute from the allowed attributes for iframe elements.

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