TYPO3CMS
CVE-2010-3659
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 · uneditedMultiple cross-site scripting (XSS) vulnerabilities in TYPO3 CMS 4.1.x 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 allow remote authenticated backend users to inject arbitrary web script or HTML via unspecified parameters to the extension manager, or unspecified parameters to unknown backend forms.
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 · moderate confidenceMultiple cross-site scripting (XSS) vulnerabilities in TYPO3 CMS allow authenticated backend users to inject arbitrary web script or HTML via unspecified parameters in the extension manager and other backend forms. The vulnerabilities affect versions 4.1.x 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.
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.0= 4.1.1= 4.1.2= 4.1.3= 4.1.4= 4.1.5= 4.1.6= 4.1.7= 4.1.8= 4.1.9= 4.1.10= 4.1.11CVSS 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.0/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.
-
Determine installed TYPO3 CMS versionLog into the TYPO3 backend and navigate to the Admin Dashboard or Help > About section to view the exact version number. Alternatively, check the VERSION file in the TYPO3 root directory if accessible.Affected if The installed version falls within 4.1.0 through 4.1.13, 4.2.0 through 4.2.12, 4.3.0 through 4.3.3, or 4.4.0 through 4.4.0.
-
Verify backend user access existsCheck if any backend user accounts are active in the TYPO3 installation by querying the be_users table in the database or reviewing user records in the backend admin panel.Affected if There is at least one authenticated backend user account enabled in the system.
-
Confirm extension manager module is accessibleLog into the backend and attempt to access the Extension Manager module (usually at /typo3/mod.php?M=tx_extmgr). Check if the current backend user has permissions to view or modify extensions.Affected if The Extension Manager module is accessible to an authenticated backend user.
You are affected if your TYPO3 CMS 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 you have authenticated backend users who can access the extension manager or other backend forms.
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 CMS to version 4.1.14, 4.2.13, 4.3.4, or 4.4.1 or later to patch the XSS vulnerabilities. If upgrading is not immediately feasible, disable unused backend extensions and implement input sanitization on backend forms.
Fix this in TYPO3
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3659 — 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-3659 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