LiveActive security incident?Get immediate response
CVE Record

CVE-2020-11063: Observable Response Discrepancy in TYPO3 CMS

In TYPO3 CMS versions 10.4.0 and 10.4.1, it has been discovered that time-based attacks can be used with the password reset functionality for backend users. This allows an attacker to mount user enumeration based on email addresses assigned to backend user accounts. This has been fixed in 10.4.2.

LowCVSS 3.7Not KEV-listedUpdated
Glexia's TakeAutomated analysislow

Security readout for executives and security teams

Plain-English summary

CVE-2020-11063 is a low-severity TYPO3 CMS issue where backend password reset behavior can reveal whether an email belongs to a backend user. This is not account takeover by itself, but it can help attackers identify administrator or staff accounts for later phishing, credential attacks, or targeted probing.

Executive priority

Treat this as a prompt but not emergency patch for affected TYPO3 sites. Prioritize internet-facing administrative backends and environments where backend user email addresses are sensitive.

Technical view

TYPO3 CMS 10.4.0 and 10.4.1 are affected by an observable response discrepancy in backend user password reset. The source describes time-based attacks enabling backend email enumeration. CVSS 3.1 is 3.7 with network access, high attack complexity, no privileges, no user interaction, and low confidentiality impact.

Likely exposure

Exposure appears limited to TYPO3 CMS 10.4.0 and 10.4.1 deployments using reachable backend password reset functionality. Systems already upgraded to 10.4.2 or later are reported fixed by the source bundle.

Exploitation context

The source bundle does not show known active exploitation, and KEV status is false. Practical impact is information disclosure through email enumeration, which is more useful as reconnaissance than as a standalone breach path.

Researcher notes

The issue maps to CWE-204 and is a timing-based observable discrepancy. Sources only support backend email enumeration, not credential compromise, code execution, or confirmed exploitation. Keep validation non-invasive and avoid production timing probes unless authorized.

Mitigation direction

  • Upgrade affected TYPO3 CMS instances to 10.4.2 or later.
  • Review the TYPO3 security advisory before scheduling remediation.
  • Restrict access to backend password reset pages where operationally feasible.
  • Monitor reset-related logs for unusual repeated requests.
  • Prioritize any internet-facing administrative TYPO3 backends.

Validation and detection

  • Inventory TYPO3 CMS versions and flag 10.4.0 or 10.4.1.
  • Confirm backend password reset functionality is not publicly exposed unnecessarily.
  • Verify upgraded systems report TYPO3 CMS 10.4.2 or later.
  • Review logs for repeated reset attempts against multiple email addresses.
  • Check vendor advisory details for any deployment-specific notes.
Prepared
Confidence
high
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · low confidence lookup

CWE-204: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

Credential and access behavior lookup

The CVE wording references authentication or credential exposure, so valid-account and credential-access review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-11063 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Low
CVSS
3.7 (3.1)
Known Exploited
No
Published

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

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
4Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
3.7CVSS 3.1LowCVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:N/A:N2.21.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

3.7Low
CVSS 3.1 vector shape for CVE-2020-11063Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
TYPO3TYPO3 CMS>= 10.4.0, <= 10.4.1Listed
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-204 · source CWE mapping

Observable Response Discrepancy

Observable Response Discrepancy represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.