# CVE-2025-59015: Insufficient Entropy in Password Generation

> Insufficient entropy in TYPO3 password generation allows attackers to brute-force passwords more easily, risking account takeover.

- **Severity:** Medium 6.3 (`CVSS:4.0/AV:N/AC:H/AT:P/PR:N/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Sep 2025
- **Updated:** 9 Sep 2025
- **Also known as:** GHSA-p5jq-5383-qvc7

## What is CVE-2025-59015?

CVE-2025-59015 is a medium-severity vulnerability in Typo3 Typo3, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A deterministic three‑character prefix in the Password Generation component of TYPO3 CMS versions 12.0.0–12.4.36 and 13.0.0–13.4.17 reduces entropy, allowing attackers to carry out brute‑force attacks more quickly.

Weakness: CWE-331 (Insufficient Entropy)

## Which versions are affected by CVE-2025-59015?

4 open source packages ship an affected version, including typo3/cms-core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `typo3/cms-core` | Packagist | From 12.0.0 | 12.4.37 |
| `typo3/cms-core` | Packagist | From 12.0.0 | 12.4.37 |
| `typo3/cms-core` | Packagist | From 13.0.0 | 13.4.18 |
| `typo3/cms-core` | Packagist | From 13.0.0 | 13.4.18 |

Products: Typo3 Typo3.

## How do I fix CVE-2025-59015?

Upgrade typo3/cms-core to a fixed version for your release line: 12.4.37 or 13.4.18.

## Is CVE-2025-59015 being exploited?

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

## Other vulnerabilities in Typo3 Typo3

- [CVE-2009-0258](https://insights.sbomify.com/CVE-2009-0258/): Indexed Search Engine for TYPO3 Command Execution via Metacharacter Injection (critical 10.0)
- [CVE-2011-3583](https://insights.sbomify.com/CVE-2011-3583/): Typo3 SQL injection due to faulty prepared statements (critical 9.8)
- [CVE-2011-4628](https://insights.sbomify.com/CVE-2011-4628/): Typo3 Authentication Bypass (critical 9.8)
- [CVE-2023-24814](https://insights.sbomify.com/CVE-2023-24814/): Persisted Cross-Site Scripting in Frontend Rendering in typo3 (high 8.8)
- [CVE-2021-41113](https://insights.sbomify.com/CVE-2021-41113/): Cross-Site-Request-Forgery in Backend URI Handling in Typo3 (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59015 and fix it if it is affected.

What it is: CVE-2025-59015 is a medium-severity vulnerability in Typo3 Typo3, published on 9 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59015 in the wild and no public exploit code.

Affected packages and fixed versions:
- typo3/cms-core (Packagist): affected from 12.0.0; fixed in 12.4.37
- typo3/cms-core (Packagist): affected from 12.0.0; fixed in 12.4.37
- typo3/cms-core (Packagist): affected from 13.0.0; fixed in 13.4.18
- typo3/cms-core (Packagist): affected from 13.0.0; fixed in 13.4.18

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-2025-59015/ (Markdown: https://insights.sbomify.com/CVE-2025-59015/index.md)
```

## Sources

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

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