How severe is CVE-2009-3628?

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

Which packages are affected by CVE-2009-3628?

CVE-2009-3628 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-3628?

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

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

Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

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

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

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

CVE-2009-3628 is classified as Information Exposure (CWE-200). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

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

CVE-2009-3628 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-3628 — cms-backend

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

TYPO3 Backend Discloses Encryption Key

Published

May 2, 2022

Updated

Feb 8, 2024

Affected

4 pkgs

Patched

3 / 4

Exploits

None indexed

Exploitation data as of Nov 7, 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 CVEs67th percentile — riskier than 67% of all scored CVEsHighest risk

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

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 determine an encryption key via crafted input to a tt_content form element.

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`

Affected Products

1 product · 59 configurations

Application

typo3typo3

≤ 4.0.12

55 versions

0.1.21.0.141.11.1.11.1.091.1.101.2.01.3.01.3.23.03.3.x3.5

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
A fix is available for CVE-2009-3628; check the affected-versions list above or the advisory for the patched release of typo3/cms-backend, then make sure no transitive dependency still pins the vulnerable range.
Workarounds
Assume what was exposed is already known: rotate any credential, token or key that the affected component could return, restrict the endpoint to callers that genuinely need it, and strip sensitive fields from responses and error output at the boundary rather than relying on the client not to read them.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2009-3628 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works