Pimcore: SQL Injection via Column Name in DateFilter allows authenticated user to extract arbitrary database data including admin password hashes
CVE-2026-55208GHSA-79cw-hfcc-7mw9
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (pimcore/studio-backend-bundle 2026.1.6, 2025.4.6), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Packagist pimcore/studio-backend-bundle
- Affected
- < 2025.4.6>= 2026.1.0, < 2026.1.6
- Fixed in
- 2026.1.6, 2025.4.6
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-79cw-hfcc-7mw9 lists affected ranges: Packagist pimcore/studio-backend-bundle >=0 =2026.1.0 <2026.1.6 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-79cw-hfcc-7mw9 lists affected ranges: Packagist pimcore/studio-backend-bundle >=0 =2026.1.0 <2026.1.6
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 7.7 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:H/I:N/A:N
- EPSS
- CVE-2026-55208: 0.41% estimated exploitation activity in the next 30 days; percentile 35.60 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary An authenticated user extracts the admin password hash and any other database content through a time-based blind SQL injection in the DateFilter column key parameter. The POST /pimcore-studio/api/website-settings endpoint (and 11 other listing endpoints) accepts a columnFilters array where the key field is interpolated directly into SQL with only manual backtick wrapping. The DateFilter uses fixed named parameters (:minTime, :maxTime), so the injected column name is not subject to PDO named parameter validation. An attacker breaks out of the backtick quoting with a backtick character and appends arbitrary SQL, including SLEEP() for time-based extraction and IF() subqueries for conditional data exfiltration. Vulnerability Details Exploitable: DateFilter with Fixed Named Parameters src/Listing/Filter/DateFilter.php lines 49-57 handle the on operator. The column key comes from user input and is placed in the SQL with manual backtick wrapping, while the named parameters are…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 2 · amended ·
Amended from ghsa record GHSA-79cw-hfcc-7mw9
- Revision 1 · created ·
Published from osv record GHSA-79cw-hfcc-7mw9
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-55208 Advisory: Pimcore: SQL Injection via Column Name in DateFilter allows authenticated user to extract arbitrary database data including admin password hashes IDs: CVE-2026-55208, GHSA-79cw-hfcc-7mw9 Record: https://patchnext.com/advisories/cve-2026-55208 (revision 2, source checked 26 Oct 2026, 14:50 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: High (CVSS 7.7) 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, 2025.4.6. A vendor fix does not mean a deployment is fixed. ## Affected components - Packagist pimcore/studio-backend-bundle: affected < 2025.4.6; >= 2026.1.0, < 2026.1.6; fixed in 2026.1.6, 2025.4.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-79cw-hfcc-7mw9 (OSV record GHSA-79cw-hfcc-7mw9 lists affected ranges: Packagist pimcore/studio-backend-bundle >=0 =2026.1.0 <2026.1.6 (fixed)) - Verified: https://github.com/advisories/GHSA-79cw-hfcc-7mw9 (GitHub-reviewed advisory GHSA-79cw-hfcc-7mw9 lists affected ranges: Packagist pimcore/studio-backend-bundle >=0 =2026.1.0 <2026.1.6) Commands are suggestions: review each one before running it.
Loading voting…