Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.1

TYPO3 Cross-Site Scripting in Filelist Module

GHSA-6xwf-7rfm-4gwc

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (typo3/cms-core 10.2.1, 9.5.12, 8.7.30), 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
    >= 10.0.0, < 10.2.1>= 8.0.0, < 8.7.30>= 9.0.0, < 9.5.12
    Fixed in
    8.7.30, 10.2.1, 9.5.12

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
EPSS
No dated EPSS signal available.
Source description

As published by the source; long descriptions are shortened.

It has been discovered that the output table listing in the “Files” backend module is vulnerable to cross-site scripting when a file extension contains malicious sequences. Access to the file system of the server - either directly or through synchronization - is required to exploit the vulnerability.

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

    Published from ghsa record GHSA-6xwf-7rfm-4gwc

Agent brief

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

# Patch Next advisory brief: GHSA-6xwf-7rfm-4gwc

Advisory: TYPO3 Cross-Site Scripting in Filelist Module
IDs: GHSA-6xwf-7rfm-4gwc
Record: https://patchnext.com/advisories/ghsa-6xwf-7rfm-4gwc (revision 1, source checked 26 Oct 2026, 14:25 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
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 10.2.1, 9.5.12, 8.7.30. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms-core: affected >= 10.0.0, < 10.2.1; >= 8.0.0, < 8.7.30; >= 9.0.0, < 9.5.12; fixed in 8.7.30, 10.2.1, 9.5.12

## Suggested inspection (read-only)
- Packagist typo3/cms-core: 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.
- 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-6xwf-7rfm-4gwc (GitHub-reviewed advisory GHSA-6xwf-7rfm-4gwc lists affected ranges: Packagist typo3/cms-core >=10.0.0 =8.0.0 =9.0.0 <9.5.12)

Commands are suggestions: review each one before running it.

Loading voting…