Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-44741 high CVSS 8.8

SQL Injection in pimcore/admin-ui-classic-bundle (CVE-2026-44741)

Summary

SQL injection in pimcore/admin-ui-classic-bundle (CVE-2026-44741). Successful exploitation can lead to full system takeover. Exploitable via POST /admin/translation/translations. Mitigation: upgrade to 1.7.18 or later.

Original description

The description as published by the source.

GitHub Security Advisory Draft — GM-369

Summary

SQL injection in Pimcore's translation grid date filter — the user-supplied property field from the filter JSON is interpolated directly into a UNIX_TIMESTAMP(DATE(FROM_UNIXTIME(...))) SQL expression without parameterization or allowlist validation.

Severity

CVSS 3.1: 8.8 (High) — AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Affected Component

  • Package: pimcore/admin-ui-classic-bundle
  • File: src/Controller/Admin/TranslationController.php
  • Lines: 565 (input), 569 (inadequate sanitization), 593 (injection point)
  • Endpoint: POST /admin/translation/translations

Description

The translation grid endpoint processes JSON filter parameters. When a filter has type: "date", the property field is extracted and used to construct a SQL expression:

$fieldname = $filter[$propertyField];              // Line 565 — user input
$fieldname = str_replace('--', '', $fieldname);    // Line 569 — trivially bypassable
$fieldname = $tableName . '.' . $fieldname;        // Line 577
$fieldname = "UNIX_TIMESTAMP(DATE(FROM_UNIXTIME({$fieldname})))";  // Line 593 — injection

The str_replace('--', '') sanitization is trivially bypassable (use /**/ comments or ----). In non-language mode, $fieldname is concatenated directly into the SQL condition without quoting or parameterization.

Impact

Authenticated user with translations view permission can extract arbitrary database data via UNION-based or…

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-44741 has been found in pimcore/admin-ui-classic-bundle.
Attackers can target a specific entry point like POST /admin/translation/translations over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade pimcore/admin-ui-classic-bundle to 1.7.18 or later.
If unsure, ask your IT team or search "pimcore/admin-ui-classic-bundle CVE-2026-44741" on the vendor's site.

CVE-2026-44741 (pimcore/admin-ui-classic-bundle) — CWE-89 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /admin/translation/translations / property / TranslationController.php
Patched: 1.7.18 — 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/admin-ui-classic-bundle. Attackers reach the vulnerable code path via POST /admin/translation/translations.

📍 Affected scope

Check the vendor advisory for the affected versions of pimcore/admin-ui-classic-bundle. Attack surface: POST /admin/translation/translations / property / TranslationController.php.

🔥 Severity

Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 1.7.18.

🛡️ 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/translation/translations requests with malformed payloads or SQL meta-characters. Run grep -r 'pimcore/admin-ui-classic-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

  1. 1
    Identify exposure identify 
    grep -r 'pimcore/admin-ui-classic-bundle' . | grep -v node_modules

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

  2. 2
    Hunt for indicators of compromise detect 
    grep 'POST /admin/translation/translations' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'

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

  3. 3
    Apply patch patch 
    Upgrade pimcore/admin-ui-classic-bundle to 1.7.18

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

  4. 4
    Post-deployment verification verify 
    Replay attack against POST /admin/translation/translations on staging to confirm patch closes the vector

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

Affected packages

composer pimcore/admin-ui-classic-bundle
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.7.18"}]}]
Packagist pimcore/admin-ui-classic-bundle
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.7.18"}]}]

References

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