CVE-2022-31046 is a medium-severity (CVSS 4.3) Information Exposure vulnerability in typo3/cms-core. O3 Security confirms whether CVE-2022-31046 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Information Disclosure via Export Module in TYPO3 CMS
Real-World Exposure
typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms-core🐘typo3/cms🐘typo3/cmsReal-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 is an open source web content management system. Prior to versions 7.6.57 ELTS, 8.7.47 ELTS, 9.5.34 ELTS, 10.4.29, and 11.5.11, the export functionality fails to limit the result set to allowed columns of a particular database table. This way, authenticated users can export internal details of database tables they already have access to. TYPO3 versions 7.6.57 ELTS, 8.7.47 ELTS, 9.5.34 ELTS, 10.4.29, 11.5.11 fix the problem described above. In order to address this issue, access to mentioned export functionality is completely denied for regular backend users.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3/cms-core | ≥ 7.0.0&&< 7.6.57 | 7.6.57 |
| 🐘Packagist | typo3/cms-core | ≥ 8.0.0&&< 8.7.47 | 8.7.47 |
| 🐘Packagist | typo3/cms-core | ≥ 9.0.0&&< 9.5.35 | 9.5.35 |
| 🐘Packagist | typo3/cms-core | ≥ 10.0.0&&< 10.4.29 | 10.4.29 |
| 🐘Packagist | typo3/cms-core | ≥ 11.0.0&&< 11.5.11 | 11.5.11 |
| 🐘Packagist | typo3/cms | ≥ 10.0.0&&< 10.4.29 | 10.4.29 |
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3/cms-core. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update typo3/cms-core to 7.6.57 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2022-31046 is resolved across your whole dependency graph.
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 pinpoints whether CVE-2022-31046 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to CVE-2022-31046. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is CVE-2022-31046 in your dependencies?
O3 detects CVE-2022-31046 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.