CVE-2022-31046

Meta

• CVSS: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C (4.0)

Problem

The export functionality fails to limit the result set to allowed columns of a particular database table. This allows authenticated users to export internal details of database tables to which they already have access.

Credits

Thanks to TYPO3 core merger Lina Wolf who reported this issue and to TYPO3 security member Torben Hansen who fixed the issue.

References

• TYPO3-CORE-SA-2022-001

CVE-2022-31046 has a CVSS score of 4.3 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (7.6.57, 8.7.47, 9.5.35, 10.4.29, 11.5.11); upgrading removes the vulnerable code path.

Kodem intelligence

Update to TYPO3 versions 7.6.57 ELTS, 8.7.47 ELTS, 9.5.35 ELTS, 10.4.29, 11.5.11 that fix the problem described above.

In order to address this issue, access to mentioned export functionality is completely denied for regular backend users.

ℹ️ Strong security defaults - Manual actions required
Following User TSconfig setting would allow using the export functionality for particular users:

options.impexp.enableExportForNonAdminUser = 1

1. What is CVE-2022-31046? CVE-2022-31046 is a medium-severity security vulnerability in typo3/cms-core (composer), affecting versions >= 7.0.0, < 7.6.57. It is fixed in 7.6.57, 8.7.47, 9.5.35, 10.4.29, 11.5.11.
2. How severe is CVE-2022-31046? CVE-2022-31046 has a CVSS score of 4.3 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2022-31046?
   • typo3/cms-core (composer) (versions >= 7.0.0, < 7.6.57)
   • typo3/cms (composer) (versions >= 10.0.0, < 10.4.29)
4. Is there a fix for CVE-2022-31046? Yes. CVE-2022-31046 is fixed in 7.6.57, 8.7.47, 9.5.35, 10.4.29, 11.5.11. Upgrade to this version or later.
5. Is CVE-2022-31046 exploitable, and should I be worried? Whether CVE-2022-31046 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2022-31046 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2022-31046?
   • Upgrade typo3/cms-core to 7.6.57 or later
   • Upgrade typo3/cms-core to 8.7.47 or later
   • Upgrade typo3/cms-core to 9.5.35 or later
   • Upgrade typo3/cms-core to 10.4.29 or later
   • Upgrade typo3/cms-core to 11.5.11 or later
   • Upgrade typo3/cms to 10.4.29 or later
   • Upgrade typo3/cms to 11.5.11 or later