How severe is CVE-2009-0258?

No CVSS score has been assigned to CVE-2009-0258 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2009-0258?

CVE-2009-0258 affects the following packages: typo3/cms (Packagist), typo3/cms (Packagist), typo3/cms (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2009-0258?

Update typo3/cms to 4.0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-0258 is resolved across your whole dependency graph.

How do I detect CVE-2009-0258 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2009-0258 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against CVE-2009-0258?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2009-0258 can be triaged on real exposure rather than presence alone.

Is CVE-2009-0258 actively exploited in the wild?

No public exploit code has been indexed for CVE-2009-0258 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2009-0258?

CVE-2009-0258 has an EPSS (Exploit Prediction Scoring System) score of 3.3%, placing it in the 88th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2009-0258?

CVE-2009-0258 is classified as Improper Input Validation (CWE-20). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2009-0258 published, and has it been updated?

CVE-2009-0258 was published on May 2, 2022 and was last updated on January 23, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CVE-2009-0258: typo3/cms

EPSS Exploitation Probability

via FIRST.org ↗

3.3%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs88th percentile — riskier than 88% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

3 pkgs affected

🐘typo3/cms🐘typo3/cms🐘typo3/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms`	≥ 4.0.0&&< 4.0.10	4.0.10`composer require typo3/cms:^4.0.10`
🐘Packagist	`typo3/cms`	≥ 4.1.0&&< 4.1.8	4.1.8`composer require typo3/cms:^4.1.8`
🐘Packagist	`typo3/cms`	≥ 4.2.0&&< 4.2.4	4.2.4`composer require typo3/cms:^4.2.4`

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update typo3/cms to 4.0.10 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-0258 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2009-0258 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2009-0258. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

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.

O3 Security · Impact-Aware SCA

Is CVE-2009-0258 in your dependencies?

O3 Security finds CVE-2009-0258 across Packagist dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works

CVE-2009-0258 — typo3/cms