TYPO3CMS
CVE-2012-1605
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 · uneditedThe Extbase Framework in TYPO3 4.6.x through 4.6.6, 4.7, and 6.0 unserializes untrusted data, which allows remote attackers to unserialize arbitrary objects and possibly execute arbitrary code via vectors related to "a missing signature (HMAC) for a request argument."
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 confidenceThe Extbase Framework in TYPO3 versions 4.6.x-4.6.6, 4.7, and 6.0 contains a PHP object injection vulnerability. The framework deserializes request arguments without HMAC signature verification, allowing remote attackers to supply malicious serialized PHP objects. When unserialized, these objects can trigger magic methods (__wakeup, __destruct, etc.) to achieve arbitrary code execution.
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.6= 4.6.0= 4.6.1= 4.6.2= 4.6.3= 4.6.4= 4.6.5= 4.6.6= 4.7= 6.0CVSS 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
- Authentication
- None
- Confidentiality
- None
- Integrity
- Partial
- Availability
- None
AV:N/AC:L/Au:N/C:N/I:P/A:N
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.
-
Identify installed TYPO3 versionCheck the TYPO3 version file (typically Version.php in the t3lib or sysext/core directory) or access the TYPO3 admin panel to view the installed version numberAffected if The installed version is 4.6.0-4.6.6, 4.7, or 6.0
-
Locate Extbase extensionCheck for the presence of the extbase extension in the typo3conf/ext/ or typo3/sysext/ directory, or view the installed extensions list in the TYPO3 extension managerAffected if Extbase extension is installed and enabled in the TYPO3 installation
-
Verify request argument handlingExamine the Extbase request handling code (typically in typo3/sysext/extbase/Classes/MVC/Request.php or similar) for use of unserialize() on request arguments without HMAC validationAffected if The code deserializes incoming request arguments (e.g., via $_GET, $_POST) without verifying an HMAC signature before unserialization
-
Check for exposed extbase actionsReview the application's extbase controllers and actions to identify endpoints that accept serialized object data in request parametersAffected if The application exposes extbase controller actions that accept and deserialize user-supplied data without validation
You are affected if your TYPO3 installation runs version 4.6.0-4.6.6, 4.7, or 6.0 with the Extbase extension enabled and your application deserializes request arguments without HMAC verification.
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 dataUpgrade to a patched TYPO3 version that implements HMAC signature validation for serialized request arguments, or disable deserialization of user-supplied data in the Extbase framework.
Fix this in TYPO3
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2012-1605 — 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-2012-1605 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