<?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>Tue, 13 Oct 2026 08:06:28 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-281269</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-281269</link>
      <description>EUVD-2026-281269</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-281269</guid>
    </item>
    <item>
      <title>fkie_cve-2026-39392</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-39392</link>
      <description>&lt;p&gt;CI4MS is a CodeIgniter 4-based CMS skeleton that delivers a production-ready, modular architecture with RBAC authorization and theme support. Prior to 0.31.4.0, the Pages module does not apply the html_purify validation rule to content fields during create and update operations, while the Blog module does. Page content is stored unsanitized in the database and rendered as raw HTML on the public frontend via echo $pageInfo-&amp;gt;content. An authenticated admin with page-editing privileges can inject arbitrary JavaScript that executes in the browser of every public visitor viewing the page. This vulnerability is fixed in 0.31.4.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;CI4MS is a CodeIgniter 4-based CMS skeleton that delivers a production-ready, modular architecture with RBAC authorization and theme support. Prior to 0.31.4.0, the Pages module does not apply the html_purify validation rule to content fields during create and update operations, while the Blog module does. Page content is stored unsanitized in the database and rendered as raw HTML on the public frontend via echo $pageInfo-&amp;gt;content. An authenticated admin with page-editing privileges can inject arbitrary JavaScript that executes in the browser of every public visitor viewing the page. This vulnerability is fixed in 0.31.4.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-39392</guid>
    </item>
    <item>
      <title>GHSA-fjpj-6qcq-6pw2 — CI4MS has stored XSS in Pages Content Due to Missing html_purify Sanitization</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-fjpj-6qcq-6pw2</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: ci4-cms-erp/ci4ms&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The Pages module does not apply the `html_purify` validation rule to content fields during create and update operations, while the Blog module does. Page content is stored unsanitized in the database and rendered as raw HTML on the public frontend via `echo $pageInfo-&amp;gt;content`. An authenticated admin with page-editing privileges can inject arbitrary JavaScript that executes in the browser of every public visitor viewing the page.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The Blog module correctly applies HTMLPurifier sanitization to content fields:&lt;/p&gt;
&lt;p&gt;**`modules/Blog/Controllers/Blog.php:82`**
```php
&amp;#39;lang.*.content&amp;#39; =&amp;gt; [&amp;#39;label&amp;#39; =&amp;gt; lang(&amp;#39;Backend.content&amp;#39;), &amp;#39;rules&amp;#39; =&amp;gt; &amp;#39;required|html_purify&amp;#39;],
```&lt;/p&gt;
&lt;p&gt;The Pages module omits this rule in both create and update methods:&lt;/p&gt;
&lt;p&gt;**`modules/Pages/Controllers/Pages.php:82`** (create)
```php
&amp;#39;lang.*.content&amp;#39; =&amp;gt; [&amp;#39;label&amp;#39; =&amp;gt; lang(&amp;#39;Backend.content&amp;#39;), &amp;#39;rules&amp;#39; =&amp;gt; &amp;#39;required&amp;#39;],
```&lt;/p&gt;
&lt;p&gt;**`modules/Pages/Controllers/Pages.php:130`** (update)
```php
&amp;#39;lang.*.content&amp;#39; =&amp;gt; [&amp;#39;label&amp;#39; =&amp;gt; lang(&amp;#39;Backend.content&amp;#39;), &amp;#39;rules&amp;#39; =&amp;gt; &amp;#39;required&amp;#39;],
```&lt;/p&gt;
&lt;p&gt;Content is stored directly without sanitization:&lt;/p&gt;
&lt;p&gt;**`modules/Pages/Controllers/Pages.php:111`** (create path)
```php
&amp;#39;content&amp;#39; =&amp;gt; $lData[&amp;#39;content&amp;#39;],
```&lt;/p&gt;
&lt;p&gt;**`modules/Pages/Controllers/Pages.php:157`** (update path)
```php
&amp;#39;content&amp;#39; =&amp;gt; $lData[&amp;#39;content&amp;#39;],
```&lt;/p&gt;
&lt;p&gt;On the public frontend, the content is rendered as raw HTML without escaping:&lt;/p&gt;
&lt;p&gt;**`app/Views/templates/default/pages.php:32`**
```php
&amp;lt;?php echo $pageInfo-&amp;gt;content ?&amp;gt;
```&lt;/p&gt;
&lt;p&gt;Note that the same…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: ci4-cms-erp/ci4ms&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The Pages module does not apply the `html_purify` validation rule to content fields during create and update operations, while the Blog module does. Page content is stored unsanitized in the database and rendered as raw HTML on the public frontend via `echo $pageInfo-&amp;gt;content`. An authenticated admin with page-editing privileges can inject arbitrary JavaScript that executes in the browser of every public visitor viewing the page.&lt;/p&gt;
&lt;p&gt;## Details&lt;/p&gt;
&lt;p&gt;The Blog module correctly applies HTMLPurifier sanitization to content fields:&lt;/p&gt;
&lt;p&gt;**`modules/Blog/Controllers/Blog.php:82`**
```php
&amp;#39;lang.*.content&amp;#39; =&amp;gt; [&amp;#39;label&amp;#39; =&amp;gt; lang(&amp;#39;Backend.content&amp;#39;), &amp;#39;rules&amp;#39; =&amp;gt; &amp;#39;required|html_purify&amp;#39;],
```&lt;/p&gt;
&lt;p&gt;The Pages module omits this rule in both create and update methods:&lt;/p&gt;
&lt;p&gt;**`modules/Pages/Controllers/Pages.php:82`** (create)
```php
&amp;#39;lang.*.content&amp;#39; =&amp;gt; [&amp;#39;label&amp;#39; =&amp;gt; lang(&amp;#39;Backend.content&amp;#39;), &amp;#39;rules&amp;#39; =&amp;gt; &amp;#39;required&amp;#39;],
```&lt;/p&gt;
&lt;p&gt;**`modules/Pages/Controllers/Pages.php:130`** (update)
```php
&amp;#39;lang.*.content&amp;#39; =&amp;gt; [&amp;#39;label&amp;#39; =&amp;gt; lang(&amp;#39;Backend.content&amp;#39;), &amp;#39;rules&amp;#39; =&amp;gt; &amp;#39;required&amp;#39;],
```&lt;/p&gt;
&lt;p&gt;Content is stored directly without sanitization:&lt;/p&gt;
&lt;p&gt;**`modules/Pages/Controllers/Pages.php:111`** (create path)
```php
&amp;#39;content&amp;#39; =&amp;gt; $lData[&amp;#39;content&amp;#39;],
```&lt;/p&gt;
&lt;p&gt;**`modules/Pages/Controllers/Pages.php:157`** (update path)
```php
&amp;#39;content&amp;#39; =&amp;gt; $lData[&amp;#39;content&amp;#39;],
```&lt;/p&gt;
&lt;p&gt;On the public frontend, the content is rendered as raw HTML without escaping:&lt;/p&gt;
&lt;p&gt;**`app/Views/templates/default/pages.php:32`**
```php
&amp;lt;?php echo $pageInfo-&amp;gt;content ?&amp;gt;
```&lt;/p&gt;
&lt;p&gt;Note that the same…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-fjpj-6qcq-6pw2</guid>
    </item>
  </channel>
</rss>
