<?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, 06 Oct 2026 20:24:12 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-335748</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-335748</link>
      <description>EUVD-2026-335748</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-335748</guid>
    </item>
    <item>
      <title>fkie_cve-2026-55212</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-55212</link>
      <description>&lt;p&gt;Pimcore is an Open Source Data &amp;amp; Experience Management Platform. Prior to 2025.4.6 and 2026.1.6, the Studio API class definition creation endpoint POST /pimcore-studio/api/class/definition/configuration-view/detail/create is guarded by the objects permission instead of the classes permission, allowing a standard editor-level user to create class definitions without admin privileges. Class definition creation generates new database tables and PHP class files on the server, and missing API-layer UID format validation allows malformed UIDs to reach model-layer validation and return internal exceptions. This issue is fixed in versions 2025.4.6 and 2026.1.6.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Pimcore is an Open Source Data &amp;amp; Experience Management Platform. Prior to 2025.4.6 and 2026.1.6, the Studio API class definition creation endpoint POST /pimcore-studio/api/class/definition/configuration-view/detail/create is guarded by the objects permission instead of the classes permission, allowing a standard editor-level user to create class definitions without admin privileges. Class definition creation generates new database tables and PHP class files on the server, and missing API-layer UID format validation allows malformed UIDs to reach model-layer validation and return internal exceptions. This issue is fixed in versions 2025.4.6 and 2026.1.6.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-55212</guid>
    </item>
    <item>
      <title>GHSA-f97c-ph8j-8vff — Pimcore: Insufficient Permission Check on Class Definition Creation Endpoint Allows Privilege Escalation</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-f97c-ph8j-8vff</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: pimcore/studio-backend-bundle&lt;/p&gt;
&lt;p&gt;### Summary
The Studio API class definition creation endpoint in `pimcore/studio-backend-bundle` is guarded by the `objects` permission instead of the `classes` permission, allowing any standard editor-level user to create class definitions without admin privileges. Class definition creation is a structural admin operation that generates new database tables and PHP class files on the server. Additionally, the API layer performs no format validation on the `uid` field before passing it to the model layer, relying solely on model-level validation that exists downstream in `ClassDefinition::saveClassInternal()`.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;### Issue 1 — Incorrect permission guard on CreateController&lt;/p&gt;
&lt;p&gt;`studio-backend-bundle/src/Class/Controller/DefinitionConfiguration/CreateController.php`:&lt;/p&gt;
&lt;p&gt;```php
#[IsGranted(UserPermissions::DATA_OBJECTS-&amp;gt;value)]
```&lt;/p&gt;
&lt;p&gt;The endpoint `POST /pimcore-studio/api/class/definition/configuration-view/detail/create` is protected by `DATA_OBJECTS` (the `objects` permission), which is a standard editor-level permission granted to content editors for creating and editing data objects. Class definition creation is a structural admin operation equivalent to schema modification, it creates new database tables and generates PHP class files on the server. This operation should require the `classes` permission, which is the permission Pimcore enforces for class definition management in the Classic Admin.&lt;/p&gt;
&lt;p&gt;Any authenticated user with object editing rights can call this endpoin…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Packagist: pimcore/studio-backend-bundle&lt;/p&gt;
&lt;p&gt;### Summary
The Studio API class definition creation endpoint in `pimcore/studio-backend-bundle` is guarded by the `objects` permission instead of the `classes` permission, allowing any standard editor-level user to create class definitions without admin privileges. Class definition creation is a structural admin operation that generates new database tables and PHP class files on the server. Additionally, the API layer performs no format validation on the `uid` field before passing it to the model layer, relying solely on model-level validation that exists downstream in `ClassDefinition::saveClassInternal()`.&lt;/p&gt;
&lt;p&gt;### Details&lt;/p&gt;
&lt;p&gt;### Issue 1 — Incorrect permission guard on CreateController&lt;/p&gt;
&lt;p&gt;`studio-backend-bundle/src/Class/Controller/DefinitionConfiguration/CreateController.php`:&lt;/p&gt;
&lt;p&gt;```php
#[IsGranted(UserPermissions::DATA_OBJECTS-&amp;gt;value)]
```&lt;/p&gt;
&lt;p&gt;The endpoint `POST /pimcore-studio/api/class/definition/configuration-view/detail/create` is protected by `DATA_OBJECTS` (the `objects` permission), which is a standard editor-level permission granted to content editors for creating and editing data objects. Class definition creation is a structural admin operation equivalent to schema modification, it creates new database tables and generates PHP class files on the server. This operation should require the `classes` permission, which is the permission Pimcore enforces for class definition management in the Classic Admin.&lt;/p&gt;
&lt;p&gt;Any authenticated user with object editing rights can call this endpoin…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-f97c-ph8j-8vff</guid>
    </item>
  </channel>
</rss>
