How severe is CVE-2009-3630?

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

Which packages are affected by CVE-2009-3630?

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

How do I fix CVE-2009-3630?

No patched version of typo3/cms-backend has shipped for CVE-2009-3630 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.

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

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

How do I mitigate CVE-2009-3630 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-3630?

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

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

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

CVE-2009-3630 has an EPSS (Exploit Prediction Scoring System) score of 2.0%, placing it in the 80th 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-3630 published, and has it been updated?

CVE-2009-3630 was published on May 2, 2022 and was last updated on February 8, 2024. 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-3630 — typo3/cms-backend

CVE-2009-3630 is a security vulnerability in typo3/cms-backend. A fix is available for typo3/cms-backend — see the affected versions and patch details below.

TYPO3 Backend vulnerable to Frame Hijacking

Published

May 2, 2022

Updated

Feb 8, 2024

Affected

4 pkgs

Patched

3 / 4

Exploits

None indexed

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

EPSS Exploitation Probability

via FIRST.org ↗

2.0%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs80th percentile — riskier than 80% 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

4 pkgs affected

🐘typo3/cms-backend🐘typo3/cms-backend🐘typo3/cms-backend🐘typo3/cms-backend

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 Backend subcomponent in TYPO3 4.0.13 and earlier, 4.1.x before 4.1.13, 4.2.x before 4.2.10, and 4.3.x before 4.3beta2 allows remote authenticated users to place arbitrary web sites in TYPO3 backend framesets via crafted parameters, related to a "frame hijacking" issue.

Affected Packages

4 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`typo3/cms-backend`	all versions	No fix
🐘Packagist	`typo3/cms-backend`	≥ 4.1.0&&< 4.1.13	4.1.13`composer require typo3/cms-backend:^4.1.13`
🐘Packagist	`typo3/cms-backend`	≥ 4.2.0&&< 4.2.10	4.2.10`composer require typo3/cms-backend:^4.2.10`
🐘Packagist	`typo3/cms-backend`	≥ 4.3alpha1&&< 4.3beta2	4.3beta2`composer require typo3/cms-backend:^4.3beta2`

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-backend, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
No patched version of typo3/cms-backend has shipped for CVE-2009-3630 yet. Where your build allows, override or pin the dependency away from the vulnerable range, and apply any maintainer-recommended mitigation.
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-3630 can be triaged on real exposure rather than presence alone.

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

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2009-3630 in your dependencies?

O3 Security finds CVE-2009-3630 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