pimcore/pimcore security advisory

CVE-2026-23492: Pimcore Has an Incomplete Patch for CVE-2023-30848

CVE-2026-23492 is a high-severity SQL injection vulnerability in the PHP package pimcore/pimcore (CVSS 4.9), published 14 January 2026. It is fixed in 12.3.1; earlier versions are affected. Exploiting it needs an admin-level account.

high 4.9 published 2026-01-14 · updated 2026-06-17

Affected versions: <= 11.5.13
>= 12.0.0-RC1, < 12.3.1
Fixed in: 12.3.1
Newest release: 2026.3.4
Severity: High · CVSS 4.9
Type: SQL injection
CWE-89
Exploited in the wild: Not on the CISA KEV list
checked 2026-11-04

Is your pimcore/pimcore version affected?

Run composer show pimcore/pimcore in your project, then enter the version. We check it against this and every other known pimcore/pimcore advisory.

Who can exploit CVE-2026-23492

Access: A high-privilege account in the app, such as an admin.

CVSS vector (scored by NVD): CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:N/A:N

Your app is only exposed if it uses the affected part of pimcore/pimcore. The advisory below says which part that is. If you are not sure, upgrade anyway: it costs less than finding out.

How to fix CVE-2026-23492 in pimcore/pimcore

Find the installed version: composer show pimcore/pimcore. If you never required it yourself, composer why pimcore/pimcore shows which package pulls it in.
Update it: composer update pimcore/pimcore --with-all-dependencies. You need 12.3.1 or newer.
If Composer will not go that high, your composer.json constraint is holding it back. Widen it (for example "pimcore/pimcore": "^12.3.1" if you can take that version), or upgrade the package that requires it.
Run composer audit. It reads the same advisory data and should no longer list CVE-2026-23492.
Commit composer.lock and deploy it. On the server, run composer install --no-dev from the lock file, not composer update.

If you cannot upgrade yet

The advisory gives this workaround:

Although CVE-2023-30848 attempted to mitigate SQL injection by removing SQL comments (--) and catching syntax errors, the fix is insufficient.

General hardening for SQL injection issues while the upgrade waits. None of it replaces the fix.

Make sure user input never reaches the affected query builder or ORM method unvalidated; allow-list column and sort names.
Give the app's database user only the permissions it needs.
If your app does not use the affected feature, note that in your audit, but still plan the upgrade.

The CVE-2026-23492 advisory

Pimcore is an Open Source Data & Experience Management Platform. Prior to 12.3.1 and 11.5.14, an incomplete SQL injection patch in the Admin Search Find API allows an authenticated attacker to perform blind SQL injection. Although CVE-2023-30848 attempted to mitigate SQL injection by removing SQL comments (--) and catching syntax errors, the fix is insufficient. Attackers can still inject SQL payloads that do not rely on comments and infer database information via blind techniques. This vulnerability affects the admin interface and can lead to database information disclosure. This vulnerability is fixed in 12.3.1 and 11.5.14.

Description from the CVE record, published by GitHub (the CVE Numbering Authority), via the NVD entry for CVE-2026-23492. Advisory title: “Pimcore Has an Incomplete Patch for CVE-2023-30848”.

References

GitHub advisory GHSA-qvr7-7g55-69xj github.com
Fix commit 25ad867 github.com

Other pimcore/pimcore advisories

Need help patching or upgrading? Laskyr does PHP and Laravel security fixes and upgrades. Tell us what you run and we reply with a plan and a price.

Ask about a fix

Where this data comes from

Affected and fixed versions: the Packagist security advisories API (GitHub Advisory Database and FriendsOfPHP), the same data composer audit uses. Synced 2026-11-03.
Description, score, weakness and references: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Exploited-in-the-wild status: the CISA Known Exploited Vulnerabilities catalog, checked 2026-11-04.
Compiled by Daniel Lasek at Laskyr from the sources above. The summary, “who can exploit it”, “how to fix it” and hardening sections are our plain-English reading of the record and are generated from it. The quoted description is the record's own text. Spot an error? Tell us.