How severe is CVE-2021-32767?

CVE-2021-32767 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by CVE-2021-32767?

CVE-2021-32767 affects the following packages: typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms-core (Packagist), typo3/cms (Packagist), typo3/cms (Packagist), typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2021-32767?

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

How do I detect CVE-2021-32767 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2021-32767 if there is no patch (or I can't update yet)?

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.

Is CVE-2021-32767 actively exploited in the wild?

No public exploit code has been indexed for CVE-2021-32767 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2021-32767?

CVE-2021-32767 has an EPSS (Exploit Prediction Scoring System) score of 0.8%, placing it in the 56th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2021-32767?

CVE-2021-32767 is classified as CWE-532 (CWE-532). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2021-32767 published, and has it been updated?

CVE-2021-32767 was published on July 20, 2021 and was last updated on August 27, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘

🐘 Packagist

Not in CISA KEV

MEDIUM severity

CVE-2021-32767 — cms-core

MEDIUMFix: TYPO3/typo3@0b49501

CVE-2021-32767 is a medium-severity (CVSS 6.5) CWE-532 vulnerability in typo3/cms-core. A fix is available for typo3/cms-core — see the affected versions and patch details below.

Information Disclosure in User Authentication

Also known asBIT-typo3-2021-32767GHSA-34fr-fhqr-7235

Published

Jul 20, 2021

Updated

Aug 27, 2026

Affected

8 pkgs

Patched

8 / 8

Exploits

None indexed

Exploitation data as of Oct 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.8%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs56th percentile — riskier than 56% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

CVE-2021-32767 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.

Where this sits among everything scored

Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.

Real-World Exposure

8 pkgs affected

🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms🐘typo3/cms🐘typo3/cms

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

Meta

CVSS: AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N/E:F/RL:O/RC:C (4.9)

Problem

It has been discovered that user credentials have been logged as plaintext when explicitly using log level debug, which is not the default configuration.

Solution

Update to TYPO3 versions 7.6.52 ELTS, 8.7.41 ELTS, 9.5.28, 10.4.18, 11.3.1 that fix the problem described.

Credits

Thanks to Ingo Schmitt who reported this issue, and to TYPO3 core & security team member Benni Mack who fixed the issue.

References

TYPO3-CORE-SA-2021-012

Affected Packages

8 total 8 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms-core`	≥ 7.0.0&&< 7.6.52	7.6.52`composer require typo3/cms-core:^7.6.52`
🐘Packagist	`typo3/cms-core`	≥ 8.0.0&&< 8.7.41	8.7.41`composer require typo3/cms-core:^8.7.41`
🐘Packagist	`typo3/cms-core`	≥ 9.0.0&&< 9.5.28	9.5.28`composer require typo3/cms-core:^9.5.28`
🐘Packagist	`typo3/cms-core`	≥ 10.0.0&&< 10.4.18	10.4.18`composer require typo3/cms-core:^10.4.18`
🐘Packagist	`typo3/cms-core`	≥ 11.0.0&&< 11.3.1	11.3.1`composer require typo3/cms-core:^11.3.1`
🐘Packagist	`typo3/cms`	≥ 10.0.0&&< 10.4.18	10.4.18`composer require typo3/cms:^10.4.18`

Affected Products

1 product · 5 configurations

Application

typo3typo3

≥ 11.0.0 && ≤ 11.3.0

range

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms-core to 7.6.52 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2021-32767 is resolved across your whole dependency graph.
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.

Frequently Asked Questions

> ### Meta > * CVSS: `AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N/E:F/RL:O/RC:C` (4.9) ### Problem It has been discovered that user credentials have been logged as plaintext when explicitly using log level debug, which is not the _default_ configuration. ### Solution Update to TYPO3 versions 7.6.52 ELTS, 8.7.41 ELTS, 9.5.28, 10.4.18, 11.3.1 that fix the problem described. ### Credits Thanks to Ingo Schmitt who reported this issue, and to TYPO3 core & security team member Benni Mack who fixed the issue. ### References * [TYPO3-CORE-SA-2021-012](https://typo3.org/security/advisory/typo3-core-sa-2021

O3 Security · Impact-Aware SCA

Is CVE-2021-32767 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

CWE Classification

CWE-532CWE-532

Weaponization

No known public exploit tooling found.

OpenSSF Scorecard

Package health score

TYPO3.CMS

6.0/10

Code-Review10/10

Maintained10/10

Branch-Protection0/10

Assessed Oct 5, 2026

Timeline

Disclosed

Jul 20, 2021

Last updated

Aug 27, 2026

Identifiers

CVE-2021-32767

GHSA-34fr-fhqr-7235

BIT-typo3-2021-32767

References

Advisorygithub.com Advisorytypo3.org Advisorynvd.nist.gov Webgithub.com Webgithub.com Webgithub.com Webgithub.com Webtypo3.org Packagegithub.com

Related vulnerabilities

This CVE is medium severity; 8 of 8 other CVEs affecting typo3/cms-core are rated as high or higher (top: high).

CVE-2026-19418CVE-2026-47352CVE-2026-47347CVE-2026-47343CVE-2026-49740CVE-2026-47348CVE-2026-49742CVE-2026-47349

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedAug 27, 2026

CVE-2021-32767 — cms-core

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Meta

Problem

Solution

Credits

References

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is CVE-2021-32767 in your dependencies?