LiveActive security incident?Get immediate response
CVE Record

CVE-2020-28917: An issue was discovered in the view_statistics (aka View frontend statistics) extension before 2.0.1 for TY...

An issue was discovered in the view_statistics (aka View frontend statistics) extension before 2.0.1 for TYPO3. It saves all GET and POST data of TYPO3 frontend requests to the database. Depending on the extensions used on a TYPO3 website, sensitive data (e.g., cleartext passwords if ext:felogin is installed) may be saved.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

A TYPO3 statistics extension could store every frontend GET and POST value in the database. If a site also collected sensitive form data, such as passwords through ext:felogin, that data could be retained in cleartext and become exposed to anyone with database or log-table access.

Executive priority

Treat this as a privacy and credential-handling issue, not a remote takeover claim. Prioritize sites that process logins or sensitive forms, because historical database contents may already contain secrets.

Technical view

CVE-2020-28917 affects the TYPO3 view_statistics extension before 2.0.1. The extension saved all TYPO3 frontend request parameters to the database, including POST bodies. The public record does not provide CVSS, CWE, exploit details, or broad product metadata beyond the extension advisory.

Likely exposure

Exposure is limited to TYPO3 sites running view_statistics before 2.0.1. Risk is higher where frontend forms handle passwords, tokens, personal data, or other secrets that could be captured in stored request data.

Exploitation context

The source bundle does not show KEV listing or active exploitation evidence. The main concern is data exposure after sensitive request values are stored, especially if database access is compromised or available to administrators who should not see secrets.

Researcher notes

Evidence is narrow but clear: affected versions store frontend GET and POST data. The public bundle lacks scoring, exploitability details, and exact database schema context, so validation should focus on extension version, installed form/auth extensions, and historical stored request fields.

Mitigation direction

  • Upgrade view_statistics to version 2.0.1 or later.
  • Review the TYPO3 advisory for vendor-specific remediation guidance.
  • Disable the extension if it is unnecessary or cannot be upgraded promptly.
  • Inspect stored statistics data for sensitive values.
  • Rotate credentials or tokens if cleartext secrets are found.

Validation and detection

  • Inventory TYPO3 installations using the view_statistics extension.
  • Confirm installed view_statistics versions are not earlier than 2.0.1.
  • Check whether frontend forms submit passwords, tokens, or personal data.
  • Review stored statistics tables for captured GET or POST values.
  • Verify post-remediation request data is no longer stored unsafely.
Prepared
Confidence
medium
Sources
3

Public sources used

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.

description · low confidence lookup

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration 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-28917 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
Unknown
CVSS
Not scored
Known Exploited
No
Published
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.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

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