SQL Injection in pimcore/studio-backend-bundle (CVE-2026-55208)
Summary
SQL injection in pimcore/studio-backend-bundle (CVE-2026-55208). Confidential information can be exposed externally. Exploitable via POST /pimcore-studio/api/website-settings. Mitigation: upgrade to 2026.1.6 or later.
Original description
The description as published by the source.
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.
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-55208 has been found in pimcore/studio-backend-bundle.
Attackers can target a specific entry point like POST /pimcore-studio/api/website-settings over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 7.7/10.
What to do: upgrade pimcore/studio-backend-bundle to 2026.1.6 or later.
If unsure, ask your IT team or search "pimcore/studio-backend-bundle CVE-2026-55208" on the vendor's site.
CVE-2026-55208 (pimcore/studio-backend-bundle) — CWE-89 / CVSS v3 7.7
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /pimcore-studio/api/website-settings / POST /login/token / POST /pimcore-studio/api/notifications / POST /pimcore-studio/api/recycle-bin
Patched: 2026.1.6 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
SQL injection (CWE-89) exists in pimcore/studio-backend-bundle. Attackers reach the vulnerable code path via POST /pimcore-studio/api/website-settings.
Check the vendor advisory for the affected versions of pimcore/studio-backend-bundle. Attack surface: POST /pimcore-studio/api/website-settings / POST /login/token / POST /pimcore-studio/api/notifications / POST /pimcore-studio/api/recycle-bin.
Severity: High (CVSS 7.7/10). Confidential information can be exposed externally.
Update to 2026.1.6.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual POST /pimcore-studio/api/website-settings requests with malformed payloads or SQL meta-characters. Run grep -r 'pimcore/studio-backend-bundle' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'pimcore/studio-backend-bundle' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
pimcore/studio-backend-bundleを grep し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /pimcore-studio/api/website-settings' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /pimcore-studio/api/website-settingsへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade pimcore/studio-backend-bundle to 2026.1.6ステージング環境で 2026.1.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /pimcore-studio/api/website-settings on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory nvd.nist.gov
- advisory github.com
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com
- web github.com