<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<feed xmlns="http://www.w3.org/2005/Atom" xml:lang="en">
  <id>https://cve.radiocsirt.org/rss/recent/all/10</id>
  <title>Most recent entries from all</title>
  <updated>2026-10-07T05:40:18.307073+00:00</updated>
  <author>
    <name>Vulnerability-Lookup</name>
    <email>csirt@opendfir.org</email>
  </author>
  <link href="https://cve.radiocsirt.org" rel="alternate"/>
  <generator uri="https://lkiesow.github.io/python-feedgen" version="1.0.0">python-feedgen</generator>
  <subtitle>Contains only the most 10 recent entries.</subtitle>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/euvd-2026-335748</id>
    <title>EUVD-2026-335748</title>
    <updated>2026-10-07T05:40:18.375499+00:00</updated>
    <content>EUVD-2026-335748</content>
    <link href="https://cve.radiocsirt.org/vuln/euvd-2026-335748"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/fkie_cve-2026-55212</id>
    <title>fkie_cve-2026-55212</title>
    <updated>2026-10-07T05:40:18.375553+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml">
        <p>Pimcore is an Open Source Data &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.</p>
      </div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/fkie_cve-2026-55212"/>
  </entry>
  <entry>
    <id>https://cve.radiocsirt.org/vuln/ghsa-f97c-ph8j-8vff</id>
    <title>GHSA-f97c-ph8j-8vff — Pimcore: Insufficient Permission Check on Class Definition Creation Endpoint Allows Privilege Escalation</title>
    <updated>2026-10-07T05:40:18.375614+00:00</updated>
    <content type="xhtml">
      <div xmlns="http://www.w3.org/1999/xhtml"><p><strong>Affected:</strong> Packagist: pimcore/studio-backend-bundle</p>
<p>### 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()`.</p>
<p>### Details</p>
<p>### Issue 1 — Incorrect permission guard on CreateController</p>
<p>`studio-backend-bundle/src/Class/Controller/DefinitionConfiguration/CreateController.php`:</p>
<p>```php
#[IsGranted(UserPermissions::DATA_OBJECTS-&gt;value)]
```</p>
<p>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.</p>
<p>Any authenticated user with object editing rights can call this endpoin…</p></div>
    </content>
    <link href="https://cve.radiocsirt.org/vuln/ghsa-f97c-ph8j-8vff"/>
  </entry>
</feed>
