Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 4.3

Information Disclosure via Export Module

CVE-2022-31046GHSA-8gmv-9hwg-w89g

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (typo3/cms-core 11.5.11, 10.4.29, 9.5.35, 8.7.47, 7.6.57; typo3/cms 11.5.11, 10.4.29), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist typo3/cms-core

    Affected
    >= 7.0.0, < 7.6.57>= 8.0.0, < 8.7.47>= 9.0.0, < 9.5.35>= 10.0.0, < 10.4.29>= 11.0.0, < 11.5.11
    Fixed in
    7.6.57, 9.5.35, 8.7.47, 10.4.29, 11.5.11

  • Packagist typo3/cms

    Affected
    >= 10.0.0, < 10.4.29>= 11.0.0, < 11.5.11
    Fixed in
    10.4.29, 11.5.11

Sources

  • GitHub Advisory Database and maintainer security advisories on GitHub

    GitHub-reviewed advisory GHSA-8gmv-9hwg-w89g lists affected ranges: Packagist typo3/cms-core >=7.0.0 =8.0.0 =9.0.0 =10.0.0 =11.0.0 =10.0.0 =11.0.0 <11.5.11

    VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
4.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2022-31046: 0.64% estimated exploitation activity in the next 30 days; percentile 50.71 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

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. Solution 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: 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

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 1 · created ·

    Published from ghsa record GHSA-8gmv-9hwg-w89g

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2022-31046

Advisory: Information Disclosure via Export Module
IDs: CVE-2022-31046, GHSA-8gmv-9hwg-w89g
Record: https://patchnext.com/advisories/cve-2022-31046 (revision 1, source checked 26 Oct 2026, 14:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 4.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/cms-core 11.5.11, 10.4.29, 9.5.35, 8.7.47, 7.6.57; typo3/cms 11.5.11, 10.4.29. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms-core: affected >= 7.0.0, < 7.6.57; >= 8.0.0, < 8.7.47; >= 9.0.0, < 9.5.35; >= 10.0.0, < 10.4.29; >= 11.0.0, < 11.5.11; fixed in 7.6.57, 9.5.35, 8.7.47, 10.4.29, 11.5.11
- Packagist typo3/cms: affected >= 10.0.0, < 10.4.29; >= 11.0.0, < 11.5.11; fixed in 10.4.29, 11.5.11

## Suggested inspection (read-only)
- Packagist typo3/cms-core: check the installed version with your package manager.
- Packagist typo3/cms: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on typo3/cms-core, typo3/cms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-8gmv-9hwg-w89g (GitHub-reviewed advisory GHSA-8gmv-9hwg-w89g lists affected ranges: Packagist typo3/cms-core >=7.0.0 =8.0.0 =9.0.0 =10.0.0 =11.0.0 =10.0.0 =11.0.0 <11.5.11)

Commands are suggestions: review each one before running it.

Loading voting…