Categories
CVE-2021-37626

Code Injection in contao/core-bundle (CVE-2021-37626)

Summary

Code injection in contao/core-bundle (CVE-2021-37626). Successful exploitation can lead to full system takeover. Mitigation: upgrade to 4.11.7 or later.

Original description

The description as published by the source.

Contao is an open source CMS that allows you to create websites and scalable web applications. In affected versions it is possible to load PHP files by entering insert tags in the Contao back end. Installations are only affected if they have untrusted back end users who have the rights to modify fields that are shown in the front end. Update to Contao 4.4.56, 4.9.18 or 4.11.7 to resolve. If you cannot update then disable the login for untrusted back end users.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

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-2021-37626 has been found in contao/core-bundle.
Successful exploitation can lead to full system takeover.
What to do: upgrade contao/core-bundle to 4.11.7 or later.
If unsure, ask your IT team or search "contao/core-bundle CVE-2021-37626" on the vendor's site.

CVE-2021-37626 (contao/core-bundle) — CWE-94
Attack vector: remote (network-reachable) / no user interaction
Patched: 4.11.7 — 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

Arbitrary code execution (CWE-94) exists in contao/core-bundle.

📍 Affected scope

Check the vendor advisory for the affected versions of contao/core-bundle.

🔥 Severity

Severity: ?. Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 4.11.7.

🛡️ 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 request patterns matching this CVE's known IOCs. Run grep -r 'contao/core-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 'contao/core-bundle' . | grep -v node_modules

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

  2. 2
    Apply patch patch
    Upgrade contao/core-bundle to 4.11.7

    ステージング環境で 4.11.7 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

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

Affected packages

Packagist contao/core-bundle
[{"type":"ECOSYSTEM","events":[{"introduced":"4.10.0"},{"fixed":"4.11.7"}]}]
Packagist contao/contao
[{"type":"ECOSYSTEM","events":[{"introduced":"4.10.0"},{"fixed":"4.11.7"}]}]

References

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