Categories
CVE-2026-44739 high CVSS 8.7

SQL Injection in pimcore/pimcore (CVE-2026-44739)

Summary

SQL injection in pimcore/pimcore (CVE-2026-44739). Confidential information can be exposed externally. Exploitable via POST /admin/bundle/customreports/custom-report/column-config. Mitigation: upgrade to 12.3.6 or later.

Original description

The description as published by the source.

Pimcore is an Open Source Data & Experience Management Platform. Prior to 11.5.17 (LTS) and 12.3.6, the columnConfigAction endpoint in bundles/CustomReportsBundle/src/Controller/Reports/CustomReportController.php passes malicious SQL configuration through CustomReportController:columnConfigAction, SqlAdapter::getColumns, SqlAdapter::buildQueryString, and Db::fetchAssociative(), allowing an attacker with the reports_config permission to use arbitrary SELECT queries, UNION statements, dangerous database functions, and error-based SQL injection to exfiltrate or manipulate database data. This issue is fixed in versions 11.5.17 (LTS) and 12.3.6.

Source: GitHub Security Advisories (Global) 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-44739 has been found in pimcore/pimcore.
Attackers can target a specific entry point like POST /admin/bundle/customreports/custom-report/column-config over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 8.7/10.
What to do: upgrade pimcore/pimcore to 12.3.6 or later.
If unsure, ask your IT team or search "pimcore/pimcore CVE-2026-44739" on the vendor's site.

CVE-2026-44739 (pimcore/pimcore) — CWE-89 / CVSS v3 8.7
Attack vector: remote (network-reachable)
Attack surface: POST /admin/bundle/customreports/custom-report/column-config
Patched: 12.3.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.

❓ What is the problem

SQL injection (CWE-89) exists in pimcore/pimcore. Attackers reach the vulnerable code path via POST /admin/bundle/customreports/custom-report/column-config.

📍 Affected scope

Check the vendor advisory for the affected versions of pimcore/pimcore. Attack surface: POST /admin/bundle/customreports/custom-report/column-config.

🔥 Severity

Severity: High (CVSS 8.7/10). Confidential information can be exposed externally.

🔧 How to fix

Update to 12.3.6.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual POST /admin/bundle/customreports/custom-report/column-config requests with malformed payloads or SQL meta-characters. Run grep -r 'pimcore/pimcore' . 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

  1. 1
    Identify exposure identify
    grep -r 'pimcore/pimcore' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で pimcore/pimcore を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Hunt for indicators of compromise detect
    grep 'POST /admin/bundle/customreports/custom-report/column-config' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

    アクセスログで POST /admin/bundle/customreports/custom-report/column-config への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。

  3. 3
    Apply patch patch
    Upgrade pimcore/pimcore to 12.3.6

    ステージング環境で 12.3.6 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。

  4. 4
    Post-deployment verification verify
    Replay attack against POST /admin/bundle/customreports/custom-report/column-config on staging to confirm patch closes the vector

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。

Affected packages

composer pimcore/pimcore
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"12.3.6"}]}]
Packagist pimcore/pimcore
[{"type":"ECOSYSTEM","events":[{"introduced":"12.0.0-RC1"},{"fixed":"12.3.6"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details