How severe is CVE-2009-0816?

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

Which packages are affected by CVE-2009-0816?

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

How do I fix CVE-2009-0816?

A fix is available for CVE-2009-0816; check the affected-versions list above or the advisory for the patched release of typo3/cms, then make sure no transitive dependency still pins the vulnerable range.

How do I detect CVE-2009-0816 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-0816 if there is no patch (or I can't update yet)?

Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

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

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

CVE-2009-0816 has an EPSS (Exploit Prediction Scoring System) score of 1.1%, placing it in the 64th 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-0816?

CVE-2009-0816 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

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

CVE-2009-0816 was published on May 2, 2022 and was last updated on September 10, 2026. 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-0816 — cms

CVE-2009-0816 is a Cross-site Scripting (XSS) vulnerability in typo3/cms. A fix is available for typo3/cms — see the affected versions and patch details below.

Typo3 Backend XSS Vulnerability

Published

May 2, 2022

Updated

Sep 10, 2026

Affected

5 pkgs

Patched

3 / 5

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

1.1%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs64th percentile — riskier than 64% of all scored CVEsHighest risk

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

Real-World Exposure

5 pkgs affected

🐘typo3/cms🐘typo3/cms🐘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

An Information Disclosure vulnerability in jumpUrl mechanism, used to track access on web pages and provided files, allows a remote attacker to read arbitrary files on a host.

The expected value of a mandatory hash secret, intended to invalidate such requests, is exposed to remote users allowing them to bypass access control by providing the correct value.

There's no authentication required to exploit this vulnerability. The vulnerability allows to read any file, the web server user account has access to.

Affected Packages

5 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms`	≥ 3.3.0	No fix
🐘Packagist	`typo3/cms`	≥ 4.0&&< 4.0.12	4.0.12`composer require typo3/cms:^4.0.12`
🐘Packagist	`typo3/cms`	≥ 4.1.0&&< 4.1.10	4.1.10`composer require typo3/cms:^4.1.10`
🐘Packagist	`typo3/cms`	≥ 4.2.0&&< 4.2.6	4.2.6`composer require typo3/cms:^4.2.6`
🐘Packagist	`typo3/cms`	all versions	No fix

Affected Products

1 product · 28 configurations

Application

typo3typo3

28 versions

4.04.0.14.0.24.0.34.0.44.0.54.0.64.0.74.0.84.0.94.0.104.0.11

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
A fix is available for CVE-2009-0816; check the affected-versions list above or the advisory for the patched release of typo3/cms, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
Escape or sanitise the affected output on the server side rather than relying on client-side filtering, and add a Content-Security-Policy that blocks inline script execution so injected markup cannot run even if it reaches the page.

Frequently Asked Questions

An Information Disclosure vulnerability in jumpUrl mechanism, used to track access on web pages and provided files, allows a remote attacker to read arbitrary files on a host. The expected value of a mandatory hash secret, intended to invalidate such requests, is exposed to remote users allowing them to bypass access control by providing the correct value. There's no authentication required to exploit this vulnerability. The vulnerability allows to read any file, the web server user account has access to.

O3 Security · Impact-Aware SCA

Is CVE-2009-0816 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works