TYPO3CMS
CVE-2010-3667
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 Spam Abuse in the native form content element.
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 confidenceTYPO3 versions prior to 4.1.14, 4.2.13, 4.3.4, and 4.4.1 contain a vulnerability in the native form content element that allows spam abuse. Attackers can exploit the form submission mechanism to send spam emails through the affected TYPO3 installation.
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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 versionCheck the TYPO3 version by accessing the admin backend (usually at /typo3/) and viewing the version information in the admin panel, or check the 'typo3/sysext/core/Classes/Utility/GeneralUtility.php' file for the VERSION constant, or look for a version file in the installation root.Affected if The installed version is prior to 4.1.14, between 4.2.0-4.2.12, between 4.3.0-4.3.3, or between 4.4.0-4.4.0 (any version in the ranges: < 4.1.14, >= 4.2.0 < 4.2.13, >= 4.3.0 < 4.3.4, >= 4.4.0 < 4.4.1)
-
Identify use of native form content elementReview the TYPO3 backend for pages containing the native form content element (Content Element Type: 'Form' or 'Form (native)'). Check the 'tt_content' database table for records with 'CType' set to 'form' or 'list_type' containing form elements.Affected if The native form content element is in use on any publicly accessible page in the TYPO3 installation
-
Verify form accessibilityInspect the page permissions and access restrictions for pages containing form content elements. Check whether these forms are accessible to anonymous/unauthenticated users by reviewing the page access settings in the TYPO3 backend or the 'pages' database table.Affected if Form content elements are accessible to unauthenticated (public) users without any login requirement
You are affected if your TYPO3 version falls within the vulnerable ranges AND the native form content element is deployed on publicly accessible pages.
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, 4.4.1 or later to patch the vulnerability. Additionally, implement form submission rate limiting and captcha controls on public-facing forms.
Fix this in TYPO3
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2010-3667 — 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-3667 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