Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐘 Packagist

CVE-2021-21357

HIGH

CVE-2021-21357 is a high-severity (CVSS 8.3) Improper Input Validation vulnerability in typo3/cms-form. O3 Security confirms whether CVE-2021-21357 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Broken Access Control in Form Framework

Also known asBIT-typo3-2021-21357GHSA-3vg7-jw9m-pc3f
Published
Mar 23, 2021
Updated
Jul 8, 2026
Affected
10 pkgs
Patched
10 / 10
Exploits
None indexed

Blast Radius

10 pkgs affected
🐘typo3/cms-form🐘typo3/cms-form🐘typo3/cms-form🐘typo3/cms-form🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms+2 more

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

TYPO3 is an open source PHP based web content management system. In TYPO3 before versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 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. This is fixed in versions 8.7.40, 9.5.25, 10.4.14, 11.1.1.

Affected Packages

10 total 10 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagisttypo3/cms-form8.0.0&&< 8.7.408.7.40
🐘Packagisttypo3/cms-form9.0.0&&< 9.5.259.5.25
🐘Packagisttypo3/cms-form10.0.0&&< 10.4.1410.4.14
🐘Packagisttypo3/cms-form11.0.0&&< 11.1.111.1.1
🐘Packagisttypo3/cms-core10.0.0&&< 10.4.1410.4.14
🐘Packagisttypo3/cms-core11.0.0&&< 11.1.111.1.1

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-form. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update typo3/cms-form to 8.7.40 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-21357 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2021-21357 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2021-21357. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

TYPO3 is an open source PHP based web content management system. In TYPO3 before versions 8.7.40, 9.5.25, 10.4.14, 11.1.1 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 direct
O3 Security · Impact-Aware SCA

Is CVE-2021-21357 in your dependencies?

O3 detects CVE-2021-21357 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.