Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 7.5

TYPO3 CMS Authentication Bypass vulnerability

GHSA-x4rj-f7m6-42c3

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (typo3/cms-core 9.3.2, 8.7.17, 7.6.30), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist typo3/cms-core

    Affected
    >= 8.0.0, < 8.7.17>= 9.0.0, < 9.3.2>= 7.0.0, < 7.6.30
    Fixed in
    7.6.30, 9.3.2, 8.7.17

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
7.5 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

It has been discovered that TYPO3’s Salted Password system extension (which is a mandatory system component) is vulnerable to Authentication Bypass when using hashing methods which are related by PHP class inheritance. In standard TYPO3 core distributions stored passwords using the blowfish hashing algorithm can be overridden when using MD5 as the default hashing algorithm by just knowing a valid username. Per default the Portable PHP hashing algorithm (PHPass) is used which is not vulnerable.

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-x4rj-f7m6-42c3

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: GHSA-x4rj-f7m6-42c3

Advisory: TYPO3 CMS Authentication Bypass vulnerability
IDs: GHSA-x4rj-f7m6-42c3
Record: https://patchnext.com/advisories/ghsa-x4rj-f7m6-42c3 (revision 1, source checked 26 Oct 2026, 14:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/cms-core 9.3.2, 8.7.17, 7.6.30. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms-core: affected >= 8.0.0, < 8.7.17; >= 9.0.0, < 9.3.2; >= 7.0.0, < 7.6.30; fixed in 7.6.30, 9.3.2, 8.7.17

## Suggested inspection (read-only)
- Packagist typo3/cms-core: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on typo3/cms-core.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-x4rj-f7m6-42c3 (GitHub-reviewed advisory GHSA-x4rj-f7m6-42c3 lists affected ranges: Packagist typo3/cms-core >=8.0.0 =9.0.0 =7.0.0 <7.6.30)

Commands are suggestions: review each one before running it.

Loading voting…