CVE-2026-55208

HIGHPre-NVD 7.77.7—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.7 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.4%, top 66% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
Elevated
7.7EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.7Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Pimcore Studio Backend Bundle is the backend bundle for Pimcore Studio. Prior to 2025.4.6 and 2026.1.6, an authenticated user can extract the admin password hash and other database content through time-based blind SQL injection in the DateFilter column key parameter. The POST /pimcore-studio/api/website-settings endpoint and other listing endpoints accept a columnFilters array where the key field is interpolated directly into SQL with manual backtick wrapping, allowing a backtick character to break out of quoting and append arbitrary SQL such as SLEEP() and IF() subqueries. This issue is fixed in versions 2025.4.6 and 2026.1.6.

CVSS v3
7.7
EG Score
7.7(medium)
EG Risk
51(Track)
EG Risk 51/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity77% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
34%
KEV
Not listed

Published

July 9, 2026

Last Modified

July 10, 2026

Advisory Details (5)

Auto-updated Jul 9, 2026
Patch available. Sources: github_release, github, github_commit, github_pr.
github_release Patch Available

2026.1.6

Patch available: pimcore/studio-backend-bundle v2026.1.6

https://github.com/pimcore/studio-backend-bundle/releases/tag/v2026.1.6
github_release Patch Available

2025.4.6

Patch available: pimcore/studio-backend-bundle v2025.4.6

https://github.com/pimcore/studio-backend-bundle/releases/tag/v2025.4.6
github_pr Patch Available

[Listing Filters]: Add improvements and unit tests

Patch available: pimcore/studio-backend-bundle v2025.4.6 (PR #1883 merged 2026-06-11)

https://github.com/pimcore/studio-backend-bundle/pull/1883
github_commit Patch Available

commit f532428cfbf4 (pimcore/studio-backend-bundle)

Patch available: pimcore/studio-backend-bundle v2025.4.6 (contains commit f532428cfbf4)

https://github.com/pimcore/studio-backend-bundle/commit/f532428cfbf4f5d6e299a13cedd5c29541802552
github Patch Available

# SQL Injection via Column Name in DateFilter allows authenticated user to extract arbitrary database data including admin password hashes · Advisory · pimcore/pimcore · GitHub

https://github.com/pimcore/pimcore/security/advisories/GHSA-79cw-hfcc-7mw9

Vendor Advisories for CVE-2026-55208(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Packagist(1)
PackageVulnerable rangeFixed inDependents
pimcore/studio-backend-bundlev0.10.21 ... v2025.4.5 (16 versions)2025.4.6—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 10× in last 7d / 54× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-08-30 06:43 UTCEG score recompute
  2. 2026-08-30 01:22 UTCEPSS rescore
  3. 2026-08-28 21:41 UTCEPSS rescore
  4. 2026-08-27 21:44 UTCEG score recompute
  5. 2026-08-27 14:25 UTCEPSS rescore
  6. 2026-08-27 00:56 UTCEG score recompute
  7. 2026-08-26 14:46 UTCEPSS rescore
  8. 2026-08-26 03:49 UTCEG score recompute
  9. 2026-08-25 13:49 UTCEPSS rescore
  10. 2026-08-24 20:19 UTCEG score recompute
  11. 2026-08-23 03:17 UTCEG score recompute
  12. 2026-08-23 00:19 UTCEPSS rescore
  13. 2026-08-22 03:36 UTCEG score recompute
  14. 2026-08-21 23:49 UTCEPSS rescore
  15. 2026-08-21 03:48 UTCEG score recompute
  16. 2026-08-20 22:55 UTCEPSS rescore
  17. 2026-08-20 01:40 UTCEG score recompute
  18. 2026-08-19 17:04 UTCEPSS rescore
  19. 2026-08-18 23:21 UTCEG score recompute
  20. 2026-08-18 13:48 UTCEPSS rescore
  21. 2026-08-17 23:38 UTCEG score recompute
  22. 2026-08-17 13:47 UTCEPSS rescore
  23. 2026-08-16 23:53 UTCEG score recompute
  24. 2026-08-16 14:56 UTCEPSS rescore
  25. 2026-08-16 12:03 UTCEG score recompute
Show 63 more
  1. 2026-08-16 02:14 UTCEPSS rescore
  2. 2026-08-15 12:26 UTCEG score recompute
  3. 2026-08-15 01:30 UTCEPSS rescore
  4. 2026-08-14 00:58 UTCEG score recompute
  5. 2026-08-13 22:00 UTCEPSS rescore
  6. 2026-08-13 01:20 UTCEG score recompute
  7. 2026-08-12 13:51 UTCEPSS rescore
  8. 2026-08-11 13:53 UTCEG score recompute
  9. 2026-08-11 02:04 UTCEG score recompute
  10. 2026-08-11 00:00 UTCEPSS rescore
  11. 2026-08-09 14:37 UTCEG score recompute
  12. 2026-08-09 13:46 UTCEPSS rescore
  13. 2026-08-09 02:48 UTCEG score recompute
  14. 2026-08-08 16:37 UTCEPSS rescore
  15. 2026-08-08 03:09 UTCEG score recompute
  16. 2026-08-06 15:42 UTCEG score recompute
  17. 2026-08-06 13:47 UTCEPSS rescore
  18. 2026-08-06 03:37 UTCEG score recompute
  19. 2026-08-05 19:17 UTCEPSS rescore
  20. 2026-08-05 01:26 UTCEG score recompute
  21. 2026-08-04 15:10 UTCEPSS rescore
  22. 2026-08-04 13:37 UTCEG score recompute
  23. 2026-08-04 10:39 UTCEPSS rescore
  24. 2026-08-03 12:55 UTCEG score recompute
  25. 2026-08-03 10:36 UTCEPSS rescore
  26. 2026-08-02 11:14 UTCEG score recompute
  27. 2026-08-02 02:27 UTCEPSS rescore
  28. 2026-08-01 11:35 UTCEG score recompute
  29. 2026-08-01 04:16 UTCEPSS rescore
  30. 2026-07-31 00:03 UTCEG score recompute
  31. 2026-07-30 16:28 UTCEPSS rescore
  32. 2026-07-30 12:12 UTCEG score recompute
  33. 2026-07-30 01:30 UTCEPSS rescore
  34. 2026-07-29 00:20 UTCEG score recompute
  35. 2026-07-28 15:37 UTCEPSS rescore
  36. 2026-07-28 00:33 UTCEG score recompute
  37. 2026-07-27 00:06 UTCEG score recompute
  38. 2026-07-26 14:54 UTCEPSS rescore
  39. 2026-07-26 12:17 UTCEG score recompute
  40. 2026-07-25 14:18 UTCEPSS rescore
  41. 2026-07-24 14:18 UTCEPSS rescore
  42. 2026-07-23 14:18 UTCEPSS rescore
  43. 2026-07-23 03:20 UTCEG score recompute
  44. 2026-07-22 14:08 UTCEPSS rescore
  45. 2026-07-21 15:25 UTCEPSS rescore
  46. 2026-07-20 17:08 UTCEPSS rescore
  47. 2026-07-19 14:31 UTCEPSS rescore
  48. 2026-07-19 14:31 UTCEPSS rescore
  49. 2026-07-19 02:29 UTCEPSS rescore
  50. 2026-07-18 10:04 UTCEPSS rescore
  51. 2026-07-16 17:03 UTCEPSS rescore
  52. 2026-07-15 16:57 UTCEPSS rescore
  53. 2026-07-15 16:57 UTCEPSS rescore
  54. 2026-07-15 02:00 UTCEPSS rescore
  55. 2026-07-15 02:00 UTCEPSS rescore
  56. 2026-07-13 22:31 UTCEPSS rescore
  57. 2026-07-13 06:13 UTCEPSS rescore
  58. 2026-07-13 06:13 UTCEPSS rescore
  59. 2026-07-12 05:46 UTCEPSS rescore
  60. 2026-07-11 08:27 UTCEPSS rescore
  61. 2026-07-11 08:27 UTCEPSS rescore
  62. 2026-07-09 21:05 UTCEG score recompute
  63. 2026-07-09 21:05 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55208?
CVE-2026-55208 is a high vulnerability published on July 9, 2026. Pimcore Studio Backend Bundle is the backend bundle for Pimcore Studio. Prior to 2025.4.6 and 2026.1.6, an authenticated user can extract the admin password hash and other database content through time-based blind SQL injection in the DateFilter column key parameter. The POST…
When was CVE-2026-55208 disclosed?
CVE-2026-55208 was first published in the National Vulnerability Database on July 9, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55208 actively exploited?
CVE-2026-55208 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 65.8% of all scored CVEs.
What is the CVSS score of CVE-2026-55208?
CVE-2026-55208 has a CVSS v3 base score of 7.7 (NVD).
How do I remediate CVE-2026-55208?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55208, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55208

Explore →

Is Your Infrastructure Affected by CVE-2026-55208?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs