How severe is CVE-2009-4160?

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

Which packages are affected by CVE-2009-4160?

CVE-2009-4160 affects the following packages: jweiland/kk-downloader (Packagist). Ecosystems affected: Packagist.

How do I fix CVE-2009-4160?

Update jweiland/kk-downloader to 1.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-4160 is resolved across your whole dependency graph.

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

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

How do I mitigate CVE-2009-4160 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.

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

No public exploit code has been indexed for CVE-2009-4160 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-4160?

CVE-2009-4160 has an EPSS (Exploit Prediction Scoring System) score of 1.2%, placing it in the 68th 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.

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

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

🐘 Packagist

Not in CISA KEV

CVE-2009-4160 — kk-downloader

CVE-2009-4160 is a security vulnerability in jweiland/kk-downloader. A fix is available for jweiland/kk-downloader — see the affected versions and patch details below.

TYPO3 Simple Download-System with Counter and Categories Vulnerable to Information Disclosure

Published

May 2, 2022

Updated

Apr 10, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Oct 31, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

1.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs68th percentile — riskier than 68% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

1 pkg affected

🐘jweiland/kk-downloader

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

Unspecified vulnerability in the Simple download-system with counter and categories (kk_downloader) extension 1.2.1 and earlier for TYPO3 allows remote attackers to obtain sensitive information via unknown attack vectors.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`jweiland/kk-downloader`	all versions	1.2.2`composer require jweiland/kk-downloader:^1.2.2`

Affected Products

1 product · 5 configurations

Application

kk downloaderkurt_kunig

≤ 1.2.1

4 versions

1.1.01.1.11.1.21.2.0

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for jweiland/kk-downloader, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update jweiland/kk-downloader to 1.2.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2009-4160 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.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2009-4160 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works