dbcve.org
TYPO3CMS

CVE-2014-3941

MEDIUM · 5.0 CVSS v2.0 Published 2014-06-03
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
59/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

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 · unedited
TYPO3 4.5.0 before 4.5.34, 4.7.0 before 4.7.19, 6.0.0 before 6.0.14, 6.1.0 before 6.1.9, and 6.2.0 before 6.2.3 allows remote attackers to have unspecified impact via a crafted HTTP Host header, related to "Host Spoofing."

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 confidence

TYPO3 CMS does not properly validate the HTTP Host header, allowing attackers to inject arbitrary values via crafted requests. This Host Spoofing vulnerability can lead to various attacks such as password reset poisoning, cache poisoning, or manipulation of generated URLs/emails.

MitigationUpgrade to TYPO3 versions 4.5.34, 4.7.19, 6.0.14, 6.1.9, or 6.2.3 or later. Alternatively, implement server-side validation to enforce allowed hostnames and reject requests with unexpected Host header values.

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
Affected:= 4.7.0= 4.7.1= 4.7.2= 4.7.3= 4.7.4= 4.7.5= 4.7.6= 4.7.7= 4.7.8= 4.7.9= 4.7.10= 4.7.11

CVSS 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
None
Integrity
Partial
Availability
None

AV:N/AC:L/Au:N/C:N/I:P/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm TYPO3 installation exists
    Look for typo3 directory or index.php file containing TYPO3 in the web root
    Affected if No TYPO3 installation found means this CVE does not apply
  2. Locate TYPO3 version file
    Check typo3/sysext/core/Composer.json or typo3/sysext/core/composer.json for the 'version' field, or look in typo3/VERSION file
    Affected if Unable to determine version prevents further vulnerability assessment
  3. Identify installed TYPO3 version
    Read the version number from the file found in previous step
    Affected if Version cannot be determined from the installation
  4. Compare version against affected range
    Check if installed version is 4.7.0, 4.7.1, 4.7.2, 4.7.3, 4.7.4, 4.7.5, 4.7.6, 4.7.7, 4.7.8, 4.7.9, 4.7.10, or 4.7.11
    Affected if Installed version matches one of these exact versions indicates the environment is affected by this CVE

A TYPO3 installation with version 4.7.0 through 4.7.11 is vulnerable to Host header spoofing attacks via improper HTTP Host header validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to TYPO3 versions 4.5.34, 4.7.19, 6.0.14, 6.1.9, or 6.2.3 or later. Alternatively, implement server-side validation to enforce allowed hostnames and reject requests with unexpected Host header values.

Fix this in TYPO3 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-3941 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-3941 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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