dbcve.org
TYPO3CMS

CVE-2011-4628

CRITICAL · 9.8 CVSS v3.1 Published 2019-11-06
Fix available
A fix is available. Upgrade to 4.3.12 / 4.4.9 or later.
See remediation →
100/100
Remediation priority · Urgent
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
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.

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

TYPO3 before versions 4.3.12, 4.4.9, and 4.5.4 contains an authentication bypass vulnerability in the backend that allows remote attackers to bypass authentication mechanisms via a crafted request. This is a critical severity flaw enabling unauthorized administrative access to the CMS.

MitigationUpgrade TYPO3 installation to version 4.3.12, 4.4.9, 4.5.4 or later. If upgrade is not immediately possible, restrict backend access via network-level controls or implement additional authentication layers.

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:>= 4.3.0, < 4.3.12>= 4.4.0, < 4.4.9>= 4.5.0, < 4.5.4

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
High
Integrity
High
Availability
High

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

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. Locate TYPO3 installation directory
    Check your web server document root for the presence of a 'typo3' directory or 'index.php' with TYPO3 signature. Common paths include /var/www/html/typo3 or similar web root locations.
    Affected if TYPO3 CMS is present on the server
  2. Identify installed TYPO3 version
    Check the VERSION file in the TYPO3 root directory (typo3/sysext/core/DESCRIPTION or look for a VERSION file in the main typo3 directory). Alternatively, access the backend login page and inspect any version information displayed, or check the 'typo3/sysext/core/Classes/Utility/GeneralUtility.php' for version constants.
    Affected if The detected version falls within any of these ranges: 4.3.0 to 4.3.11, 4.4.0 to 4.4.8, or 4.5.0 to 4.5.3
  3. Verify backend accessibility
    Attempt to access the TYPO3 backend login page at /typo3/ on your domain (e.g., https://example.com/typo3/). Confirm the page loads and displays the TYPO3 backend login form.
    Affected if The backend interface is reachable over the network (internet or internal network)
  4. Compare version against affected ranges
    If version is 4.3.x, check if it is less than 4.3.12. If version is 4.4.x, check if less than 4.4.9. If version is 4.5.x, check if less than 4.5.4.
    Affected if Installed version is 4.3.0-4.3.11, 4.4.0-4.4.8, or 4.5.0-4.5.3

If TYPO3 is installed AND the backend is network-accessible AND the version falls within 4.3.0-4.3.11, 4.4.0-4.4.8, or 4.5.0-4.5.3, then the environment is affected by this authentication bypass vulnerability.

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 4.3.12 / 4.4.9 / 4.5.4 or later
Fixed in 4.3.124.4.94.5.4
Interim mitigation

Upgrade TYPO3 installation to version 4.3.12, 4.4.9, 4.5.4 or later. If upgrade is not immediately possible, restrict backend access via network-level controls or implement additional authentication layers.

Recommended fix High confidence

TYPO3 4.5.4 or later (recommended: latest 4.5.x stable release)

  1. Create a complete backup of the TYPO3 database and all files
  2. Place the site in maintenance mode to prevent user access during upgrade
  3. Download the appropriate fixed TYPO3 version (4.3.12, 4.4.9, or 4.5.4 or later) from the official TYPO3 repository
  4. Replace the core TYPO3 files with the new version, preserving local configuration in typo3conf/localconf.php and any custom extensions
  5. Run the TYPO3 install tool to update the database schema if needed
  6. Clear all caches via the install tool or by removing typo3temp/*
  7. Verify backend authentication is working correctly
  8. Remove maintenance mode and monitor for any issues
Caveat Upgrading across 4.x major versions carries risk of extension incompatibility; test thoroughly in a staging environment first

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

Fix this in TYPO3 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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