Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2021-21357

Vulnerability in typo3/cms-form (CVE-2021-21357)

Summary

Vulnerability in typo3/cms-form (CVE-2021-21357). Data can be tampered with by attackers. Mitigation: upgrade to 11.1.1 or later.

Original description

The description as published by the source.

Problem

Due to improper input validation, attackers can by-pass restrictions of predefined options and submit arbitrary data in the Form Designer backend module of the Form Framework.

In the default configuration of the Form Framework this allows attackers to explicitly allow arbitrary mime-types for file uploads - however, default fileDenyPattern successfully blocked files like .htaccess or malicious.php. Besides that, attackers can persist those files in any writable directory of the corresponding TYPO3 installation.

A valid backend user account with access to the form module is needed to exploit this vulnerability.

Solution

Update to TYPO3 versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 that fix the problem described.

Credits

Thanks to Richie Lee who reported this issue and to TYPO3 contributor Ralf Zimmermann who fixed the issue.

References

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-21357 has been found in typo3/cms-form.
Data can be tampered with by attackers.
What to do: upgrade typo3/cms-form to 11.1.1 or later.
If unsure, ask your IT team or search "typo3/cms-form CVE-2021-21357" on the vendor's site.

CVE-2021-21357 (typo3/cms-form) — CWE-20
Attack vector: remote (network-reachable) / no user interaction
Patched: 11.1.1 — 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-20) exists in typo3/cms-form.

📍 Affected scope

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

🔥 Severity

Severity: ?. Data can be tampered with by attackers.

🔧 How to fix

Update to 11.1.1.

🛡️ 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-form' . 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-form' . | grep -v node_modules

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

  2. 2
    Apply patch patch 
    Upgrade typo3/cms-form to 11.1.1

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

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

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

Affected packages

Packagist typo3/cms-form
[{"type":"ECOSYSTEM","events":[{"introduced":"11.0.0"},{"fixed":"11.1.1"}]}]
Packagist typo3/cms-core
[{"type":"ECOSYSTEM","events":[{"introduced":"9.0.0"},{"fixed":"9.5.25"}]}]
Packagist typo3/cms
[{"type":"ECOSYSTEM","events":[{"introduced":"9.0.0"},{"fixed":"9.5.25"}]}]

References

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