<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://vulnerability.circl.lu</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Mon, 28 Sep 2026 11:14:47 +0000</lastBuildDate>
    <item>
      <title>fkie_cve-2026-61825</title>
      <link>https://vulnerability.circl.lu/vuln/fkie_cve-2026-61825</link>
      <description>&lt;p&gt;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::RAW_HTML` 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 RAW_HTML functionality where it is not required.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;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::RAW_HTML` 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 RAW_HTML functionality where it is not required.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/fkie_cve-2026-61825</guid>
    </item>
    <item>
      <title>GHSA-vj3q-vp3g-j9c8 — code16/sharp has a stored XSS via data-html-content Sanitizer Bypass</title>
      <link>https://vulnerability.circl.lu/vuln/ghsa-vj3q-vp3g-j9c8</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: code16/sharp&lt;/p&gt;
&lt;p&gt;### Impact
The vulnerability allows an attacker to bypass the HTML sanitizer by using the `data-html-content` attribute in the content of a `SharpEditorFormField`.&lt;/p&gt;
&lt;p&gt;### Patches
The field must now explicitly configure `SharpFormEditorField::RAW_HTML` in the toolbar to keep this behavior. **When using the  `RAW_HTML` button, the application using `code16/sharp` must sanitize manually the content coming from the field**. 
Vulnerability has been patched in version 9.22.5.&lt;/p&gt;
&lt;p&gt;### Workarounds
Sanitize every contents of editors manually (e.g. using Symfony/HtmlSanitizer)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: code16/sharp&lt;/p&gt;
&lt;p&gt;### Impact
The vulnerability allows an attacker to bypass the HTML sanitizer by using the `data-html-content` attribute in the content of a `SharpEditorFormField`.&lt;/p&gt;
&lt;p&gt;### Patches
The field must now explicitly configure `SharpFormEditorField::RAW_HTML` in the toolbar to keep this behavior. **When using the  `RAW_HTML` button, the application using `code16/sharp` must sanitize manually the content coming from the field**. 
Vulnerability has been patched in version 9.22.5.&lt;/p&gt;
&lt;p&gt;### Workarounds
Sanitize every contents of editors manually (e.g. using Symfony/HtmlSanitizer)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://vulnerability.circl.lu/vuln/ghsa-vj3q-vp3g-j9c8</guid>
    </item>
  </channel>
</rss>
