TYPO3CMS
CVE-2010-3662
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 · uneditedTYPO3 before 4.1.14, 4.2.x before 4.2.13, 4.3.x before 4.3.4 and 4.4.x before 4.4.1 allows SQL Injection on the backend.
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 confidenceSQL injection vulnerability in TYPO3 CMS backend affecting versions before 4.1.14, 4.2.13, 4.3.4, and 4.4.1. The vulnerability allows attackers to manipulate database queries through unsanitized input in backend functionality.
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
< 4.1.14>= 4.2.0, < 4.2.13>= 4.3.0, < 4.3.4>= 4.4.0, < 4.4.1CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm TYPO3 CMS is installedLook for the typo3/ directory in the web root or check for TYPO3-specific files such as index.php with TYPO3 branding, typo3conf/ directory, or the TYPO3 installer.Affected if The presence of TYPO3 files indicates an installed instance.
-
Identify the installed TYPO3 versionCheck the TYPO3 version file. Common locations include: the VERSION file in the web root, the 'About' module in the TYPO3 backend (Help > About), or the typo3/sysext/core/class.t3lib_version.php file if accessible.Affected if The detected version falls into one of these ranges: < 4.1.14, >= 4.2.0 and < 4.2.13, >= 4.3.0 and < 4.3.4, or >= 4.4.0 and < 4.4.1.
-
Verify backend access is enabledConfirm the TYPO3 backend (typo3/) is accessible and functional. Check that the backend login interface at /typo3/ is reachable and not disabled via configuration.Affected if The backend interface is accessible, as this SQL injection flaw resides in backend functionality.
-
Compare version to affected rangesDocument the exact version number (for example, 4.3.2 or 4.4.0) and verify whether it is less than the fixed versions: 4.1.14, 4.2.13, 4.3.4, or 4.4.1.Affected if Your installed version is lower than any of these four fixed versions.
You are affected if TYPO3 CMS is installed with a version lower than 4.1.14, 4.2.13, 4.3.4, or 4.4.1, and the backend interface is accessible.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor data4.1.144.2.134.3.4
Upgrade TYPO3 installation to version 4.1.14, 4.2.13, 4.3.4, 4.4.1 or later to receive the patched code. If upgrading is not feasible, apply the specific vendor patch for this CVE.
Fix this in TYPO3
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2010-3662 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2010-3662 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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