TYPO3CMS
CVE-2013-1842
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 · uneditedSQL injection vulnerability in the Extbase Framework in TYPO3 4.5.x before 4.5.24, 4.6.x before 4.6.17, 4.7.x before 4.7.9, and 6.0.x before 6.0.3 allows remote attackers to execute arbitrary SQL commands via unspecified vectors, related to "the Query Object Model and relation values."
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's Extbase Framework allows remote attackers to execute arbitrary SQL commands via unspecified vectors in the Query Object Model's handling of relation values. This affects multiple 4.x and 6.0.x versions before the patched releases.
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.5= 4.5.0= 4.5.1= 4.5.2= 4.5.3= 4.5.4= 4.5.5= 4.5.6= 4.5.7= 4.5.8= 4.5.9= 4.5.10CVSS 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
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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 TYPO3 installation versionCheck the file 'typo3/sysext/core/Classes/Information/Typo3Version.php' or use the TYPO3 backend (Admin Tools > About) to view the installed version numberAffected if The installed version is 4.5.x (4.5.0 through 4.5.23) or 6.0.x (6.0.0 through 6.0.2)
-
Verify Extbase Framework is installedCheck for the existence of the 'typo3/sysext/extbase' directory or list installed system extensions in the TYPO3 backend (Extension Manager > Installed Extensions)Affected if Extbase extension is present and loaded in the TYPO3 installation
-
Identify custom Extbase repository classesSearch the directory 'typo3conf/ext/' for files matching the pattern 'Classes/Domain/Repository/*.php' and review any repository classes that implement query logic using the Query Object ModelAffected if Custom Extbase repository classes exist that perform queries involving relation fields (hasOne, hasMany, manyToMany relationships)
-
Check for vulnerable query patterns in repositoriesReview Extbase repository files for usage of $query->equals() or $query->contains() methods on relation properties, particularly where user-supplied input may flow into relation field handlingAffected if Repository queries handle relation values without proper parameter binding or sanitization
You are affected if TYPO3 version is 4.5.x before 4.5.24 or 6.0.x before 6.0.3, AND the Extbase Framework extension is installed with custom repository queries handling relations.
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 TYPO3 to version 4.5.24+, 4.6.17+, 4.7.9+, or 6.0.3+ to receive the patched Query Object Model. Review custom Extbase repository queries that handle relations for potential similar patterns.
Fix this in TYPO3
Scoped from the published advisory
- Consultation3.0 h
- Implementation4.0 h
- Testing6.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 $4,128.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-1842 — 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-2013-1842 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