<?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>Fri, 02 Oct 2026 10:00:51 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-308604</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-308604</link>
      <description>EUVD-2026-308604</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-308604</guid>
    </item>
    <item>
      <title>fkie_cve-2026-5394</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-5394</link>
      <description>&lt;p&gt;An authenticated administrative user who can import or save DataObject class definitions can inject attacker-controlled composite index metadata and trigger unintended SQL execution in the backend.&lt;/p&gt;
&lt;p&gt;This issue affects pimcore: 12.3.3.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;An authenticated administrative user who can import or save DataObject class definitions can inject attacker-controlled composite index metadata and trigger unintended SQL execution in the backend.&lt;/p&gt;
&lt;p&gt;This issue affects pimcore: 12.3.3.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-5394</guid>
    </item>
    <item>
      <title>GHSA-r2f4-ff2p-xc64 — Pimcore Platform - SQL Injection in DataObject composite index handling during class definition import/save</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-r2f4-ff2p-xc64</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: pimcore/pimcore&lt;/p&gt;
&lt;p&gt;My name is Oscar Uribe, Security Researcher at Fluid Attacks. I am reaching out because we have identified a security vulnerability in Pimcore 12.3.3 that we would like to report to you so we can coordinate a responsible disclosure together.&lt;/p&gt;
&lt;p&gt;As part of our standard disclosure measures, we follow a timeline (outlined at https://fluidattacks.com/advisories/policy), which is aligned with ISO/IEC 29147:2018 and ISO/IEC 30111:2019. In short, the timeline works as follows: we ask for acknowledgment of the report within a few days of your first accessing it, and from there, we are happy to coordinate a joint disclosure date with you, typically within 90 days of the initial discovery. This gives your team reasonable time to assess, develop, and release a fix.&lt;/p&gt;
&lt;p&gt;We have reserved the CVE ID **&amp;#34;CVE-2026-5394&amp;#34;** for this issue, and the advisory will eventually be published at [https://fluidattacks.com/advisories/dragons](https://fluidattacks.com/advisories/dragons). We are committed to coordinating the timing of that publication with you.&lt;/p&gt;
&lt;p&gt;Please feel free to reach out if you have any questions about the report, the process, or the timeline. We are glad to work with you on this.&lt;/p&gt;
&lt;p&gt;## Description
An authenticated administrative user who can import or save DataObject class definitions can inject attacker-controlled composite index metadata and trigger unintended SQL execution in the backend.&lt;/p&gt;
&lt;p&gt;The vulnerable flow accepts `compositeIndices` from imported JSON, stores the values without stric…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: pimcore/pimcore&lt;/p&gt;
&lt;p&gt;My name is Oscar Uribe, Security Researcher at Fluid Attacks. I am reaching out because we have identified a security vulnerability in Pimcore 12.3.3 that we would like to report to you so we can coordinate a responsible disclosure together.&lt;/p&gt;
&lt;p&gt;As part of our standard disclosure measures, we follow a timeline (outlined at https://fluidattacks.com/advisories/policy), which is aligned with ISO/IEC 29147:2018 and ISO/IEC 30111:2019. In short, the timeline works as follows: we ask for acknowledgment of the report within a few days of your first accessing it, and from there, we are happy to coordinate a joint disclosure date with you, typically within 90 days of the initial discovery. This gives your team reasonable time to assess, develop, and release a fix.&lt;/p&gt;
&lt;p&gt;We have reserved the CVE ID **&amp;#34;CVE-2026-5394&amp;#34;** for this issue, and the advisory will eventually be published at [https://fluidattacks.com/advisories/dragons](https://fluidattacks.com/advisories/dragons). We are committed to coordinating the timing of that publication with you.&lt;/p&gt;
&lt;p&gt;Please feel free to reach out if you have any questions about the report, the process, or the timeline. We are glad to work with you on this.&lt;/p&gt;
&lt;p&gt;## Description
An authenticated administrative user who can import or save DataObject class definitions can inject attacker-controlled composite index metadata and trigger unintended SQL execution in the backend.&lt;/p&gt;
&lt;p&gt;The vulnerable flow accepts `compositeIndices` from imported JSON, stores the values without stric…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-r2f4-ff2p-xc64</guid>
    </item>
  </channel>
</rss>
