TYPO3CMS
CVE-2010-3669
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.2.13, 4.3.x before 4.3.4 and 4.4.x before 4.4.1 allows XSS and Open Redirection in the frontend login box.
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 versions before 4.2.13, 4.3.x before 4.3.4, and 4.4.x before 4.4.1 contain cross-site scripting (XSS) and open redirection vulnerabilities in the frontend login box. Attackers can inject malicious scripts or manipulate redirect parameters to phishing or malicious 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.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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Confirm TYPO3 installation existsCheck for the presence of TYPO3 by looking for the index.php file in the web root or the typo3 directory. Alternatively, access the TYPO3 backend by navigating to /typo3 on the web server.Affected if TYPO3 is not installed on the system.
-
Determine installed TYPO3 versionLog in to the TYPO3 backend and navigate to Help > About. Alternatively, check the file typo3/sysext/core/ChangeLog or the constant file that defines TYPO3_version. You can also create a simple PHP script to echo the TYPO3_VERSION constant if available.Affected if Unable to determine the version, making comparison with affected ranges impossible.
-
Compare version against affected rangesVerify that the installed version falls within any of these ranges: 4.2.0 to 4.2.12, 4.3.0 to 4.3.3, or 4.4.0. If the version is 4.2.13, 4.3.4, 4.4.1 or later, the system is NOT affected by this CVE.Affected if The installed version is 4.2.x where x < 13, OR 4.3.x where x < 4, OR 4.4.0.
-
Verify frontend login box is accessibleCheck if the frontend login plugin (typically via EXT:felogin or the built-in login box) is enabled on any public-facing pages. Access the TYPO3 backend, go to Web > Page, and search for login forms or check the TypoScript template for plugin configurations containing 'felogin' or 'login' settings.Affected if The frontend login box is not in use, the attack surface is reduced but the software version may still be vulnerable.
A system is affected if TYPO3 is installed with version 4.2.x before 4.2.13, 4.3.x before 4.3.4, or 4.4.0, and the frontend login box functionality is enabled and accessible to users.
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.2.134.3.44.4.1
Upgrade TYPO3 to version 4.2.13, 4.3.4, 4.4.1 or later. Alternatively, apply vendor-supplied patches for the frontend login box component.
Fix this in TYPO3
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3669 — 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-3669 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