CVE-2020-25025 — l10nmgr
MEDIUMCVE-2020-25025 is a medium-severity (CVSS 4.3) CWE-863 vulnerability in localizationteam/l10nmgr. A fix is available for localizationteam/l10nmgr — see the affected versions and patch details below.
Incorrect Authorization in TYPO3 extension
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
CVE-2020-25025 by exploitation likelihood (EPSS) against impact (CVSS). Outside the shaded patch-first corner.
Where this sits among everything scored
Of 385,738 CVEs with a current EPSS score, this one falls in the < 10% band (highlighted). Counts from FIRST.org, log-scaled.
Real-World Exposure
localizationteam/l10nmgr🐘localizationteam/l10nmgr🐘localizationteam/l10nmgrReal-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 l10nmgr (aka Localization Manager) extension before 7.4.0, 8.x before 8.7.0, and 9.x before 9.2.0 for TYPO3 allows Information Disclosure (translatable fields).
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | localizationteam/l10nmgr | all versions | 7.4.0composer require localizationteam/l10nmgr:^7.4.0 |
| 🐘Packagist | localizationteam/l10nmgr | ≥ 8.0.0&&< 8.7.0 | 8.7.0composer require localizationteam/l10nmgr:^8.7.0 |
| 🐘Packagist | localizationteam/l10nmgr | ≥ 9.0.0&&< 9.2.0 | 9.2.0composer require localizationteam/l10nmgr:^9.2.0 |
Affected Products
localization managerlocalization_manager_projectDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for localizationteam/l10nmgr, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update localizationteam/l10nmgr to 7.4.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2020-25025 is resolved across your whole dependency graph.
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
Is CVE-2020-25025 in your dependencies?
Find it across Packagist, including transitive dependencies.