Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2020-26229

XXE (XML External Entity) in typo3/cms-core (CVE-2020-26229)

Summary

Vulnerability in typo3/cms-core (CVE-2020-26229). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 10.4.10 or later.

Original description

The description as published by the source.

Problem

It has been discovered that RSS widgets are susceptible to XML external entity processing.
This vulnerability is reasonable, but is theoretical - it was not possible to actually reproduce the vulnerability with current PHP versions of supported and maintained system distributions.

At least with libxml2 version 2.9, the processing of XML external entities is disabled per default - and cannot be exploited. Besides that, a valid backend user account is needed.

Solution

Update to TYPO3 version 10.4.10 that fixes the problem described.

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-2020-26229 has been found in typo3/cms-core.
Risk of unauthorized operations or information disclosure.
What to do: upgrade typo3/cms-core to 10.4.10 or later.
If unsure, ask your IT team or search "typo3/cms-core CVE-2020-26229" on the vendor's site.

CVE-2020-26229 (typo3/cms-core) — CWE-611
Attack vector: remote (network-reachable)
Patched: 10.4.10 — 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

A vulnerability (CWE-611) exists in typo3/cms-core.

📍 Affected scope

Check the vendor advisory for the affected versions of typo3/cms-core.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 10.4.10.

🛡️ 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 'typo3/cms-core' . 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 'typo3/cms-core' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade typo3/cms-core to 10.4.10

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

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

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

Affected packages

Packagist typo3/cms-core
[{"type":"ECOSYSTEM","events":[{"introduced":"10.0.0"},{"fixed":"10.4.10"}]}]
Packagist typo3/cms
[{"type":"ECOSYSTEM","events":[{"introduced":"10.0.0"},{"fixed":"10.4.10"}]}]

References

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