Pimcore: Insufficient Permission Check on Class Definition Creation Endpoint Allows Privilege Escalation

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

7.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N

EPSS

• CVE-2026-55212: 0.35% estimated exploitation activity in the next 30 days; percentile 28.85 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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()`.

Details

Issue 1 — Incorrect permission guard on CreateController `studio-backend-bundle/src/Class/Controller/DefinitionConfiguration/CreateController.php`: ```php #[IsGranted(UserPermissions::DATA_OBJECTS->value)] ``` The endpoint `POST /pimcore-studio/api/class/definition/configuration-view/detail/create` is protected by `DATA_OBJECTS` (the `objects` permission), which…

Published by the source

28 Aug 2026, 19:05 UTC

Last modified by the source

10 Sep 2026, 03:51 UTC

Source last checked

23 Oct 2026, 22:04 UTC

1. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-f97c-ph8j-8vff

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-55212

Advisory: Pimcore: Insufficient Permission Check on Class Definition Creation Endpoint Allows Privilege Escalation
IDs: CVE-2026-55212, GHSA-f97c-ph8j-8vff
Record: https://patchnext.com/advisories/cve-2026-55212 (revision 1, source checked 23 Oct 2026, 22:04 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: pimcore/studio-backend-bundle 2026.1.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist pimcore/studio-backend-bundle: affected < 2026.1.6; >= 2026.1.0, < 2026.1.6; fixed in 2026.1.6

## Suggested inspection (read-only)
- Packagist pimcore/studio-backend-bundle: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on pimcore/studio-backend-bundle.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-f97c-ph8j-8vff (OSV record GHSA-f97c-ph8j-8vff lists affected ranges: Packagist pimcore/studio-backend-bundle >=0 =2026.1.0 <2026.1.6 (fixed))

Commands are suggestions: review each one before running it.