<?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://cve.radiocsirt.org</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, 05 Oct 2026 11:22:48 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-291643</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-291643</link>
      <description>EUVD-2026-291643</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-291643</guid>
    </item>
    <item>
      <title>fkie_cve-2026-24906</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-24906</link>
      <description>&lt;p&gt;October is a Content Management System (CMS) and web platform. Versions prior to 3.7.14 and 4.1.10 contain a Stored Cross-Site Scripting (XSS) vulnerability in the Backend Editor Settings. The Markup Classes fields (used for paragraph styles, inline styles, table styles, etc.) did not sanitize input to valid CSS class name characters. Malicious values were rendered unsanitized in Froala editor dropdown menus, allowing JavaScript execution when any user opened a RichEditor. Exploitation could lead to privilege escalation if a superuser opens any RichEditor during routine content editing (e.g., editing a blog post), and requires authenticated backend access with editor settings permissions. This issue has been fixed in versions 3.7.14 and 4.1.10. To workaround this issue, restrict editor settings permissions to fully trusted administrators only&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;October is a Content Management System (CMS) and web platform. Versions prior to 3.7.14 and 4.1.10 contain a Stored Cross-Site Scripting (XSS) vulnerability in the Backend Editor Settings. The Markup Classes fields (used for paragraph styles, inline styles, table styles, etc.) did not sanitize input to valid CSS class name characters. Malicious values were rendered unsanitized in Froala editor dropdown menus, allowing JavaScript execution when any user opened a RichEditor. Exploitation could lead to privilege escalation if a superuser opens any RichEditor during routine content editing (e.g., editing a blog post), and requires authenticated backend access with editor settings permissions. This issue has been fixed in versions 3.7.14 and 4.1.10. To workaround this issue, restrict editor settings permissions to fully trusted administrators only&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-24906</guid>
    </item>
    <item>
      <title>GHSA-6qmh-j78v-ffp7 — October CMS has Stored XSS in Backend Editor Markup Classes</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-6qmh-j78v-ffp7</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: october/system&lt;/p&gt;
&lt;p&gt;A stored cross-site scripting (XSS) vulnerability was identified in the Backend Editor Settings. The Markup Classes fields (used for paragraph styles, inline styles, table styles, etc.) did not sanitize input to valid CSS class name characters. Malicious values were rendered unsanitized in Froala editor dropdown menus, allowing JavaScript execution when any user opened a RichEditor.&lt;/p&gt;
&lt;p&gt;### Impact
- Stored XSS via editor settings rendered in RichEditor dropdowns
- Could allow privilege escalation if a superuser opens any RichEditor (e.g., editing a blog post)
- Requires authenticated backend access with editor settings permissions
- Triggers on routine content editing operations&lt;/p&gt;
&lt;p&gt;### Patches
The vulnerability has been patched in v3.7.14 and v4.1.10. All users are encouraged to upgrade to the latest patched version.&lt;/p&gt;
&lt;p&gt;### Workarounds
If upgrading immediately is not possible:
- Restrict editor settings permissions to fully trusted administrators only&lt;/p&gt;
&lt;p&gt;### References
- Reported by [Chris Alupului](https://github.com/neosprings)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: october/system&lt;/p&gt;
&lt;p&gt;A stored cross-site scripting (XSS) vulnerability was identified in the Backend Editor Settings. The Markup Classes fields (used for paragraph styles, inline styles, table styles, etc.) did not sanitize input to valid CSS class name characters. Malicious values were rendered unsanitized in Froala editor dropdown menus, allowing JavaScript execution when any user opened a RichEditor.&lt;/p&gt;
&lt;p&gt;### Impact
- Stored XSS via editor settings rendered in RichEditor dropdowns
- Could allow privilege escalation if a superuser opens any RichEditor (e.g., editing a blog post)
- Requires authenticated backend access with editor settings permissions
- Triggers on routine content editing operations&lt;/p&gt;
&lt;p&gt;### Patches
The vulnerability has been patched in v3.7.14 and v4.1.10. All users are encouraged to upgrade to the latest patched version.&lt;/p&gt;
&lt;p&gt;### Workarounds
If upgrading immediately is not possible:
- Restrict editor settings permissions to fully trusted administrators only&lt;/p&gt;
&lt;p&gt;### References
- Reported by [Chris Alupului](https://github.com/neosprings)&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-6qmh-j78v-ffp7</guid>
    </item>
  </channel>
</rss>
