dbcve.org
TYPO3CMS

CVE-2010-3674

MEDIUM · 6.1 CVSS v3.1 Published 2019-11-05
Fix available
A fix is available. Upgrade to 4.4.1 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 before 4.4.1 allows XSS in the frontend search 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 confidence

Cross-site scripting (XSS) vulnerability in TYPO3 CMS versions prior to 4.4.1 allows attackers to inject malicious scripts via the frontend search box input field.

MitigationUpgrade TYPO3 to version 4.4.1 or later to patch the XSS vulnerability in the frontend search functionality.

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.4.1
Debian LinuxOperating system
Affected:= 5.0

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
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

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

  1. Confirm TYPO3 installation
    Check for TYPO3 by looking for its typical directory structure (typo3/ folder) or index.php with TYPO3 signature in the web root.
    Affected if TYPO3 is not present on the system.
  2. Identify TYPO3 version
    Check the TYPO3 version by accessing the admin backend (usually /typo3/), looking for a VERSION or RELEASE file in the TYPO3 installation directory, or querying the system using TYPO3's built-in version reporting.
    Affected if The installed version is less than 4.4.1.
  3. Verify frontend search is accessible
    Confirm that the frontend search functionality is enabled and accessible on the website by visiting the search page or checking the TypoScript configuration for the search plugin.
    Affected if The frontend search feature is enabled and accessible to users.
  4. Confirm version is within vulnerable range
    Compare your installed TYPO3 version number against the affected range (anything below 4.4.1).
    Affected if The installed version is < 4.4.1 AND the frontend search is active.

You are affected if TYPO3 CMS version below 4.4.1 is installed and the frontend search functionality is enabled and accessible on your website.

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
Upgrade available Upgrade to 4.4.1 or later
Fixed in 4.4.1
Interim mitigation

Upgrade TYPO3 to version 4.4.1 or later to patch the XSS vulnerability in the frontend search functionality.

Fix this in TYPO3 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Check whether your project pulls in CVE-2010-3674 — 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-2010-3674 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