Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Critical, CVSS 9.8

Typo3 Authentication Bypass

CVE-2011-4628GHSA-79gv-5cgx-x6rx

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (typo3/cms 4.5.4, 4.4.9, 4.3.12), 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

    Affected
    < 4.3.12>= 4.4.0, < 4.4.9>= 4.5.0, < 4.5.4
    Fixed in
    4.5.4, 4.4.9, 4.3.12

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
9.8 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2011-4628: 1.65% estimated exploitation activity in the next 30 days; percentile 76.48 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

TYPO3 before 4.3.12, 4.4.x before 4.4.9, and 4.5.x before 4.5.4 allows remote attackers to bypass authentication mechanisms in the backend through a crafted request.

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

    Published from ghsa record GHSA-79gv-5cgx-x6rx

Agent brief

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

# Patch Next advisory brief: CVE-2011-4628

Advisory: Typo3 Authentication Bypass
IDs: CVE-2011-4628, GHSA-79gv-5cgx-x6rx
Record: https://patchnext.com/advisories/cve-2011-4628 (revision 1, source checked 26 Oct 2026, 14:14 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/cms 4.5.4, 4.4.9, 4.3.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms: affected < 4.3.12; >= 4.4.0, < 4.4.9; >= 4.5.0, < 4.5.4; fixed in 4.5.4, 4.4.9, 4.3.12

## Suggested inspection (read-only)
- Packagist typo3/cms: 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.
- 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-79gv-5cgx-x6rx (GitHub-reviewed advisory GHSA-79gv-5cgx-x6rx lists affected ranges: Packagist typo3/cms >=0 =4.4.0 =4.5.0 <4.5.4)

Commands are suggestions: review each one before running it.

Loading voting…