TYPO3CMS
CVE-2010-3668
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 Header Injection in the secure download feature jumpurl.
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 confidenceTYPO3 CMS before versions 4.1.14, 4.2.13, 4.3.4, and 4.4.1 contains a header injection vulnerability in the secure download feature's jumpurl parameter. The lack of proper input validation allows attackers to inject arbitrary HTTP headers into server responses via the jumpurl parameter, potentially enabling HTTP response splitting attacks, XSS, or session hijacking.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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 TYPO3 installation versionCheck the VERSION file in the TYPO3 root directory, or access the TYPO3 admin panel and navigate to About > Version. Alternatively, check the typo3/sysext/core/Classes/Utility/GeneralUtility.php or similar core files for version constants.Affected if The installed version is less than 4.1.14, OR between 4.2.0 and 4.2.12 inclusive, OR between 4.3.0 and 4.3.3 inclusive, OR between 4.4.0 and 4.4.0 inclusive.
-
Confirm secure download feature is activeCheck TYPO3 configuration files (localconf.php or LocalConfiguration.php) for enabled extensions related to secure downloads, or review if the jumpurl functionality is being used in the web server configuration or typo3conf/localconf.php.Affected if The secure download feature or jumpurl functionality is enabled and accessible on the affected TYPO3 installation.
-
Test jumpurl parameter for header injectionSend a crafted HTTP request to the TYPO3 installation using the jumpurl parameter with CRLF characters (e.g., index.php?eID=tx_cms&jumpurl=...test%0D%0AHeader:+Value). Inspect the HTTP response headers for any injected content.Affected if The server response includes arbitrary headers that were injected via the jumpurl parameter, indicating successful header injection.
The environment is affected if TYPO3 version is 4.1.x before 4.1.14, 4.2.x before 4.2.13, 4.3.x before 4.3.4, or 4.4.x before 4.4.1 AND the secure download jumpurl feature is enabled and 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 to TYPO3 4.1.14, 4.2.13, 4.3.4, or 4.4.1 or later, or apply the available security patch to implement proper input sanitization on the jumpurl parameter in the secure download feature.
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-2010-3668 — 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-3668 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