dbcve.org
TYPO3CMS

CVE-2009-0258

HIGH · 10.0 CVSS v2.0 Published 2009-01-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
The Indexed Search Engine (indexed_search) system extension in TYPO3 4.0.0 through 4.0.9, 4.1.0 through 4.1.7, and 4.2.0 through 4.2.3 allows remote attackers to execute arbitrary commands via a crafted filename containing shell metacharacters, which is not properly handled by the command-line indexer.

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

The indexed_search system extension in TYPO3 versions 4.0.0-4.2.3 contains a command injection vulnerability. The command-line indexer processes filenames without proper sanitization, allowing attackers to embed shell metacharacters in filenames to execute arbitrary commands on the server.

MitigationUpgrade TYPO3 to version 4.0.10, 4.1.8, or 4.2.4 or later, which contain the patched indexed_search extension. Alternatively, disable the indexed_search extension if not needed.

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.0= 4.0.1= 4.0.2= 4.0.3= 4.0.4= 4.0.5= 4.0.6= 4.0.7= 4.0.8= 4.0.9= 4.1.0= 4.1.1

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
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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. Identify TYPO3 core version
    Check the version.php file in the TYPO3 root directory or look at the 'TYPO3_VERSION' constant in the installation. Common path: typo3/sysext/core/version.php
    Affected if The installed version is 4.0.0 through 4.2.3 (or specifically 4.0.x through 4.1.x as listed)
  2. Locate indexed_search extension
    Check for the indexed_search extension in typo3/sysext/indexed_search/ or via the Extension Manager in the TYPO3 backend
    Affected if The indexed_search extension is installed and enabled
  3. Identify CLI indexer script
    Look for the indexer_cli.php script in the indexed_search extension directory (typo3/sysext/indexed_search/cli/indexer_cli.php)
    Affected if The CLI indexer script exists in the installation
  4. Check for scheduled/indexer cron jobs
    Review system cron jobs or scheduled tasks for commands running indexer_cli.php, typically found in /etc/cron.d/, crontab -e, or similar
    Affected if A cron job or automated task invokes the CLI indexer on uploaded file names
  5. Verify file processing permissions
    Examine the typo3conf/localconf.php or database for upload directories and check if uploaded files can have arbitrary filenames processed by the indexer
    Affected if Users can upload files with custom filenames that the indexer will process

A user is affected if TYPO3 version is 4.0.0-4.2.3 AND the indexed_search extension with its CLI indexer is installed and actively processing filenames from user-uploaded content.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade TYPO3 to version 4.0.10, 4.1.8, or 4.2.4 or later, which contain the patched indexed_search extension. Alternatively, disable the indexed_search extension if not needed.

Recommended fix High confidence

TYPO3 4.2.4 or later (or the latest 4.x release in your respective branch: 4.0.10+, 4.1.8+, or 4.2.4+)

  1. 1. Backup your TYPO3 installation and database before making any changes
  2. 2. Identify your current TYPO3 version in the TYPO3 admin backend or typo3conf/localconf.php
  3. 3. Upgrade to TYPO3 4.2.4 or later (or at minimum 4.0.10+, 4.1.8+, depending on your branch)
  4. 4. After upgrade, clear all caches via Install Tool > Important Actions > Clear all caches
  5. 5. Verify the indexed_search extension is updated to the patched version
Caveat Minor version upgrades within 4.x typically have low risk, but test in staging first; ensure PHP version compatibility with target TYPO3 version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in TYPO3 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
24.0 hours of engineering $4,160
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,656.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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