TYPO3CMS
CVE-2010-3661
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 Open Redirection 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 confidenceTYPO3 CMS contains an open redirection vulnerability in the backend interface. The application accepts untrusted input containing a URL value and redirects users to that URL without proper validation, allowing attackers to craft malicious links that redirect victims to arbitrary external sites.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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.
-
Determine installed TYPO3 versionLog into the TYPO3 backend and view the footer page, or access the Install Tool (typo3/install/) and check the 'Important helpers' or 'Database Analyzer' section which displays the version, or check the version file in typo3/sysext/core/version.phpAffected if The displayed version falls into any 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
-
Confirm backend interface is accessibleVerify that the TYPO3 backend (/typo3/ or /admin/) is enabled and reachable on your installationAffected if The backend interface is active and accepts logins or can be accessed without being explicitly disabled in configuration
-
Identify vulnerable redirect parameter usageExamine backend URLs for parameters that control redirection destinations, such as redirect= or returnUrl= parameters in login, logout, or navigation links; these should be inspected in the source code of typo3/mod/login/ or related backend modulesAffected if The backend accepts redirect parameters in URLs without validating that the destination is a trusted internal path (checking for proper allowlist or validation logic)
You are affected if your TYPO3 version is below 4.4.1 (and below the respective branch thresholds) AND the backend interface is accessible AND unvalidated redirect parameters exist in backend URL handling.
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 to version 4.1.14, 4.2.13, 4.3.4, or 4.4.1 or later. Implement proper validation of redirect parameters to ensure only trusted destinations are allowed.
Fix this in TYPO3
Scoped from the published advisory
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3661 — 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-3661 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