dbcve.org
TYPO3CMS

CVE-2011-3583

CRITICAL · 9.8 CVSS v3.1 Published 2019-11-26
Fix available
A fix is available. Upgrade to after 4.5.5 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
It was found that Typo3 Core versions 4.5.0 - 4.5.5 uses prepared statements that, if the parameter values are not properly replaced, could lead to a SQL Injection vulnerability. This issue can only be exploited if two or more parameters are bound to the query and at least two come from user input.

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

SQL injection vulnerability in Typo3 Core versions 4.5.0-4.5.5 where prepared statement parameter values are not properly replaced. Exploitation requires two or more query parameters with at least two originating from user input, allowing attackers to inject malicious SQL code through unsanitized input.

MitigationUpgrade Typo3 Core to version 4.5.6 or later which contains the fix for proper parameter binding; alternatively, apply vendor-supplied patch if immediate upgrade is not feasible.

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.5.0, <= 4.5.5

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
    Search for the 'typo3' folder in the web document root. Typical paths include /var/www/html/typo3, /home/*/public_html/typo3, or C:\inetpub\wwwroot\typo3. Check for the presence of typo3/sysext/core/ directory.
    Affected if Typo3 is not installed - the vulnerability does not apply.
  2. Determine installed Typo3 Core version
    Open the file typo3/sysext/core/ClassLoader.php and locate the line containing 'VERSION' or 'TYPO3_version'. Alternatively, access the Typo3 Install Tool at /typo3/install/ and view the 'All Configuration' section which displays the installed version.
    Affected if Unable to read version file - manual verification required.
  3. Compare version against affected range
    Verify the installed version number falls within 4.5.0 through 4.5.5 inclusive. The vulnerable versions are: 4.5.0, 4.5.1, 4.5.2, 4.5.3, 4.5.4, and 4.5.5.
    Affected if Version is 4.5.0, 4.5.1, 4.5.2, 4.5.3, 4.5.4, or 4.5.5 - the environment falls within the affected version range.
  4. Confirm database layer uses prepared statements
    Review custom extensions or site-specific Typo3 code that executes database queries. Look for usage of $GLOBALS['TYPO3_DB']->preparePreparedStatement() or similar methods that accept multiple parameters where at least two originate from user input ($_GET, $_POST, or tslib_fe::GPvars).
    Affected if The system uses prepared statements with multiple parameters where 2+ originate from user input - exploitation may be possible if version is vulnerable.

If Typo3 Core version is between 4.5.0 and 4.5.5 inclusive AND the installation uses prepared statement queries with multiple parameters from user input, the environment is affected by CVE-2011-3583.

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 a release after 4.5.5
Interim mitigation

Upgrade Typo3 Core to version 4.5.6 or later which contains the fix for proper parameter binding; alternatively, apply vendor-supplied patch if immediate upgrade is not feasible.

Recommended fix High confidence

TYPO3 4.5.6 or latest 4.5.x LTS

  1. 1. Backup your TYPO3 installation and database before proceeding
  2. 2. Download TYPO3 4.5.6 or later (preferably the latest 4.5.x LTS version) from typo3.org
  3. 3. Replace the core files in your installation with the files from the fixed version
  4. 4. Clear all caches (typo3temp folder and any caching framework data)
  5. 5. Verify the installation by logging into the TYPO3 backend
  6. 6. Test critical frontend and backend functionality to ensure the upgrade did not break existing features
Caveat Minor point upgrades within 4.5.x typically have no breaking changes, but test in staging first

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

Fix this in TYPO3 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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