Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.5

Privilege Escalation in TYPO3 CMS

GHSA-v5jp-4h2p-j2p4

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (typo3/cms 8.0.1, 7.6.5, 6.2.20), 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

    Affected
    >= 6.2.0, < 6.2.20>= 7.6.0, < 7.6.5>= 8.0.0, < 8.0.1
    Fixed in
    6.2.20, 7.6.5, 8.0.1

Sources

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

As published by the source; long descriptions are shortened.

The workspace/ version preview link created by a privileged (backend) user could be abused to obtain certain editing permission, if the admin panel is configured to be shown. A valid preview link is required to exploit this 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-v5jp-4h2p-j2p4

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-v5jp-4h2p-j2p4

Advisory: Privilege Escalation in TYPO3 CMS
IDs: GHSA-v5jp-4h2p-j2p4
Record: https://patchnext.com/advisories/ghsa-v5jp-4h2p-j2p4 (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.5)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/cms 8.0.1, 7.6.5, 6.2.20. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms: affected >= 6.2.0, < 6.2.20; >= 7.6.0, < 7.6.5; >= 8.0.0, < 8.0.1; fixed in 6.2.20, 7.6.5, 8.0.1

## Suggested inspection (read-only)
- 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.
- 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-v5jp-4h2p-j2p4 (GitHub-reviewed advisory GHSA-v5jp-4h2p-j2p4 lists affected ranges: Packagist typo3/cms >=6.2.0 =7.6.0 =8.0.0 <8.0.1)

Commands are suggestions: review each one before running it.

Loading voting…