dbcve.org
TYPO3CMS

CVE-2024-25118

MEDIUM · 6.5 CVSS v3.1 Published 2024-02-13
Fix available
A fix is available. Upgrade to 8.7.57 / 9.5.46 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable 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
TYPO3 is an open source PHP based web content management system released under the GNU GPL. Password hashes were being reflected in the editing forms of the TYPO3 backend user interface. This allowed attackers to crack the plaintext password using brute force techniques. Exploiting this vulnerability requires a valid backend user account. Users are advised to update to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, 13.0.1 that fix the problem described. There are no known workarounds for this issue.

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

In TYPO3 CMS, password hashes for backend users were being exposed in the editing forms of the backend user interface. An authenticated attacker with backend access could view these hashes and perform offline brute force attacks to recover plaintext passwords.

MitigationUpdate to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, or 13.0.1 to receive the security patch.

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:>= 8.0.0, < 8.7.57>= 9.0.0, < 9.5.46>= 10.0.0, < 10.4.43>= 11.0.0, < 11.5.35>= 12.0.0, < 12.4.11= 13.0.0

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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. Check TYPO3 version installed
    Log into the TYPO3 backend and navigate to the 'About TYPO3' module (Admin Tools > About), or check the version in the file typo3/syseems/core/Classes/Information/Typo3Version.php or composer.json in the installation root.
    Affected if The installed version falls within any of these ranges: 8.0.0 to 8.7.56, 9.0.0 to 9.5.45, 10.0.0 to 10.4.42, 11.0.0 to 11.5.34, 12.0.0 to 12.4.10, or exactly 13.0.0.
  2. Verify backend user module access
    Log into the TYPO3 backend with an administrator account and navigate to the User Management section (usually under Admin Tools > User Settings or the 'Users' module depending on version).
    Affected if You have access to view or edit backend user accounts.
  3. Inspect backend user edit form for password hash visibility
    Open an existing backend user account for editing. Locate the password field and inspect the form value or HTML source. If a long alphanumeric string resembling a password hash (typically starting with $2y$, $P$, or similar bcrypt/argon2 formats) appears in the password field rather than being blank or masked, the vulnerability is present.
    Affected if The password field displays a plaintext password hash string instead of being empty or masked.

You are affected if your TYPO3 version is within the affected ranges AND you can view backend user accounts in the backend, with password hashes visibly exposed in the user edit form.

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 8.7.57 / 9.5.46 / 10.4.43 or later
Fixed in 8.7.579.5.4610.4.43
Interim mitigation

Update to TYPO3 versions 8.7.57 ELTS, 9.5.46 ELTS, 10.4.43 ELTS, 11.5.35 LTS, 12.4.11 LTS, or 13.0.1 to receive the security patch.

Recommended fix High confidence

8.7.57 ELTS / 9.5.46 ELTS / 10.4.43 ELTS / 11.5.35 LTS / 12.4.11 LTS / 13.0.1 (depending on current major version)

  1. 1. Identify the currently installed TYPO3 version from the backend or composer.json
  2. 2. Determine the appropriate target version based on your current major version: for v8.x upgrade to 8.7.57, for v9.x upgrade to 9.5.46, for v10.x upgrade to 10.4.43, for v11.x upgrade to 11.5.35
  3. 3. Back up the database and files before upgrading
  4. 4. Run composer update typo3/cms-core to update to the target version, or use the official TYPO3 installer/extension manager
  5. 5. Clear all caches after the upgrade (via Install Tool or command line)
  6. 6. Verify backend access and test that password hash fields are no longer exposed in user editing forms
Caveat Cross-major version upgrades (e.g., v8 to v11) may introduce breaking changes; consult TYPO3 upgrade guides

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

Fix this in TYPO3 Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,370
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-25118 — 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-2024-25118 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