NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐘
🐘 Packagist
Not in CISA KEV
MEDIUM severity

CVE-2010-3671 — cms-install

MEDIUMFix: TYPO3/typo3@199cc2d

CVE-2010-3671 is a medium-severity (CVSS 6.5) CWE-384 vulnerability in typo3/cms-install. A fix is available for typo3/cms-install — see the affected versions and patch details below.

TYPO3 is vulnerable to Session Fixation

Published
Updated
Affected
4 pkgs
Patched
4 / 4
Exploits
None indexed
Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
1.6%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs75th percentile — riskier than 75% of all scored CVEsHighest risk
0.41%0.97%1.53%2.09%0.9%1.6%Apr 26Aug 26Oct 26

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

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

4 pkgs affected
🐘typo3/cms-install🐘typo3/cms-install🐘typo3/cms-install🐘typo3/cms-install

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

TYPO3 before 4.1.14, 4.2.x before 4.2.13, 4.3.x before 4.3.4 and 4.4.x before 4.4.1 is open to a session fixation attack which allows remote attackers to hijack a victim's session.

Affected Packages

4 total 4 fixed
EcosystemPackageVulnerable rangeFix
🐘Packagisttypo3/cms-installall versions4.1.14composer require typo3/cms-install:^4.1.14
🐘Packagisttypo3/cms-install≥ 4.2.0&&< 4.2.134.2.13composer require typo3/cms-install:^4.2.13
🐘Packagisttypo3/cms-install≥ 4.3.0&&< 4.3.44.3.4composer require typo3/cms-install:^4.3.4
🐘Packagisttypo3/cms-install≥ 4.4.0&&< 4.4.14.4.1composer require typo3/cms-install:^4.4.1

Affected Products

1 product · 4 configurations
Application
typo3typo3
≥ 4.4.0 && < 4.4.1
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

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

  2. Fix

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

  3. Workarounds

    Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.

Frequently Asked Questions

TYPO3 before 4.1.14, 4.2.x before 4.2.13, 4.3.x before 4.3.4 and 4.4.x before 4.4.1 is open to a session fixation attack which allows remote attackers to hijack a victim's session.
O3 Security · Impact-Aware SCA

Is CVE-2010-3671 in your dependencies?

Find it across Packagist, including transitive dependencies.

Scan my dependencies How O3 SCA works
CVE-2010-3671: cms-install — Fixed in 4.1.14