TYPO3CMS
CVE-2007-1081
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 · uneditedThe start function in class.t3lib_formmail.php in TYPO3 before 4.0.5, 4.1beta, and 4.1RC1 allows attackers to inject arbitrary email headers via unknown vectors. NOTE: some details were obtained from third party information.
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 confidenceThe start function in class.t3lib_formmail.php in TYPO3 before versions 4.0.5, 4.1beta, and 4.1RC1 contains an email header injection vulnerability. Attackers can inject arbitrary email headers (likely via CRLF injection) by manipulating input fields in the form mail component, enabling spam distribution, email spoofing, or phishing attacks via the affected server's mail system.
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.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
- Authentication
- None
- Confidentiality
- Partial
- Integrity
- Partial
- Availability
- Partial
AV:N/AC:L/Au:N/C:P/I:P/A:P
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.
-
Locate TYPO3 installation directorySearch the web server document root for the typo3 directory, which contains the core TYPO3 installation files.Affected if TYPO3 is installed on the server in any directory.
-
Identify TYPO3 version numberOpen the file typo3/version.php or check the VERSION file in the TYPO3 root directory to read the installed version number.Affected if The version is 4.0.4 or lower, or any version 4.1 through 4.1RC1.
-
Find the vulnerable form mail scriptLocate class.t3lib_formmail.php in the t3lib/ subdirectory of the TYPO3 installation.Affected if This file exists in the installation, indicating the form mail component is present.
-
Check if form mail feature is enabledReview the TYPO3 backend configuration or extension manager to determine if the form mail (formmail) extension or the t3lib form mail functionality is active or installed.Affected if The form mail component is enabled or installed on the system.
A system is affected if it runs any TYPO3 version 4.0.4 or below, or any 4.1.x version through 4.1RC1, and has the class.t3lib_formmail.php file present with the form mail feature enabled or installed.
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 to version 4.0.5 or later (or to a supported version if the 4.x branch is no longer maintained) to patch the vulnerable form mail component.
Fix this in TYPO3
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2007-1081 — 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-2007-1081 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