Pimcore ENV Variables and Cookie Informations are exposed in http_error_log
Published 15 Jan 2026 · Updated 3 Feb 2026
Affected packages
- Affected
- >=12.0.0-RC1 <12.3.1
- Fixed in
- 12.3.1
composer require pimcore/pimcore:^12.3.1- Affected
- <11.5.14
- Fixed in
- 11.5.14
composer require pimcore/pimcore:^11.5.14Details
Summary
The http_error_log file stores the $_COOKIE and $_SERVER variables, which means sensitive information such as database passwords, cookie session data, and other details can be accessed or recovered through the Pimcore backend.
Details
It’s better to remove both lines, as this information makes little sense in this context anyway.
https://github.com/pimcore/pimcore/blob/12.x/bundles/SeoBundle/src/EventListener/ResponseExceptionListener.php#L92 https://github.com/pimcore/pimcore/blob/12.x/bundles/SeoBundle/src/EventListener/ResponseExceptionListener.php#L93
PoC
In the Pimcore backend, navigate to "Search Engine Optimization" and click on "HTTP Errors." Double-click on an entry to view its details. Here, you may find sensitive data exposed.
Impact
Pimcore backend users can access sensitive environment variables, potentially exposing critical information.
Is GHSA-q433-j342-rp9h in any of your client repos?
Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected pimcore/pimcore, and gives you the command that fixes it.
References
- Linkgithub.com/pimcore/pimcore/security/advisories/GHSA-q433-j342-rp9h
- Advisorynvd.nist.gov/vuln/detail/CVE-2026-23493
- Linkgithub.com/pimcore/pimcore/pull/18918
- Linkgithub.com/pimcore/pimcore/commit/002ec7d5f84973819236796e5b314703b58e8601
- Packagegithub.com/pimcore/pimcore
- Linkgithub.com/pimcore/pimcore/releases/tag/v11.5.14
- Linkgithub.com/pimcore/pimcore/releases/tag/v12.3.1
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.