dbcve.org
TYPO3CMS

CVE-2025-59015

MEDIUM · 6.5 CVSS v3.1 Published 2025-09-09
Fix available
A fix is available. Upgrade to 12.4.37 / 13.4.18 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The TYPO3 CMS Password Generation component uses a deterministic three-character prefix, meaning the first three characters of generated passwords are predictable rather than random. This significantly reduces the effective entropy of generated passwords, allowing attackers to reduce the keyspace and perform brute-force attacks more efficiently.

MitigationUpgrade TYPO3 CMS to version 12.4.37 or 13.4.18 or later to receive the patched password generation component with improved entropy.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
TYPO3CMS
Affected:>= 12.0.0, < 12.4.37>= 13.0.0, < 13.4.18

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed TYPO3 version
    Check the version file (typo3/sysext/core/Classes/Information/Typo3Version.php) or run 'composer show typo3/cms-core' to see the installed version
    Affected if Version is >= 12.0.0 and < 12.4.37, or >= 13.0.0 and < 13.4.18
  2. Check for generated backend user passwords
    Review backend user records in the be_users database table; look for user accounts created or modified where passwords may have been generated using the TYPO3 password generator
    Affected if Any backend user accounts exist that were created using the built-in password generator in an affected version
  3. Check for generated frontend user passwords
    Review frontend user records in the fe_users database table for accounts that may have had passwords generated through TYPO3 administrative tools
    Affected if Any frontend user accounts exist with passwords generated through the vulnerable component
  4. Verify password generation feature usage
    Check access logs or admin activity logs for usage of the password generation functionality (typically found in User Admin > Backend Users or Extension Manager for certain extensions)
    Affected if The password generation tool was used to create passwords in an affected TYPO3 installation

A system is affected if it runs a TYPO3 version in the ranges 12.0.0-12.4.36 or 13.0.0-13.4.17 AND any user passwords were generated using the built-in password generation component.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 12.4.37 / 13.4.18 or later
Fixed in 12.4.3713.4.18
Interim mitigation

Upgrade TYPO3 CMS to version 12.4.37 or 13.4.18 or later to receive the patched password generation component with improved entropy.

Recommended fix High confidence

TYPO3 12.4.37 or 13.4.18 (latest available in respective branch)

  1. 1. Back up the TYPO3 database and file system before upgrading.
  2. 2. Review the TYPO3 upgrade guide for your current version at https://docs.typo3.org/.
  3. 3. Upgrade TYPO3 to version 12.4.37 or later for the 12.x branch, or to version 13.4.18 or later for the 13.x branch.
  4. 4. Run the database analyzer in the TYPO3 install tool to apply any required database migrations.
  5. 5. Clear all caches after the upgrade.
  6. 6. Verify that the password generation functionality works correctly and test admin login.
Caveat Review TYPO3 release notes for breaking changes between your current version and the target version; major version jumps (e.g., 12 to 13) may have significant breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in TYPO3 Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-59015 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-59015 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data