# CVE-2020-28917: Information disclosure in n/a

> The View frontend statistics extension logs sensitive data, including cleartext passwords, to the database, exposing them to attackers with database access.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Nov 2020
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-8886-48wg-hx3v

## What is CVE-2020-28917?

CVE-2020-28917 is a medium-severity vulnerability in n/a, published on 18 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

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.

Weakness: CWE-312 (Cleartext Storage of Sensitive Information)

## Which versions are affected by CVE-2020-28917?

It affects 1 product.


Products: View Frontend Statistics Project View Frontend Statistics.

## How do I fix CVE-2020-28917?

No fix has been published for CVE-2020-28917 yet. Limit exposure of the affected software until one is available.

## Is CVE-2020-28917 being exploited?

There is no known exploitation of CVE-2020-28917 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2020-28917 and fix it if it is affected.

What it is: CVE-2020-28917 is a medium-severity vulnerability in n/a, published on 18 Nov 2020. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2020-28917 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2020-28917/ (Markdown: https://insights.sbomify.com/CVE-2020-28917/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2020-28917
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2020-28917
- OSV: https://osv.dev/vulnerability/CVE-2020-28917

---
From sbomify Insights: https://insights.sbomify.com/CVE-2020-28917/
Summaries are generated and may contain mistakes; the official description above is the record.