Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
High, CVSS 8.1

Extbase for TYPO3 allows RCE

CVE-2016-5091GHSA-jxg5-35fj-ccwf

What to do

Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.

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-extbase

    Affected
    < 6.2.24>= 7.0, < 7.6.8>= 8.1.1, <= 8.1.1
    Fixed in
    6.2.24, 7.6.8

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
8.1 · CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
  • CVE-2016-5091: 3.38% estimated exploitation activity in the next 30 days; percentile 88.80 (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.

Extbase in TYPO3 4.3.0 before 6.2.24, 7.x before 7.6.8, and 8.1.1 allows remote attackers to obtain sensitive information or possibly execute arbitrary code via a crafted Extbase action.

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

    Published from ghsa record GHSA-jxg5-35fj-ccwf

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-2016-5091

Advisory: Extbase for TYPO3 allows RCE
IDs: CVE-2016-5091, GHSA-jxg5-35fj-ccwf
Record: https://patchnext.com/advisories/cve-2016-5091 (revision 1, source checked 26 Oct 2026, 14:06 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 8.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: typo3/cms-extbase 7.6.8, 6.2.24. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms-extbase: affected < 6.2.24; >= 7.0, < 7.6.8; >= 8.1.1, <= 8.1.1; fixed in 6.2.24, 7.6.8

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

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on typo3/cms-extbase.
- 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-jxg5-35fj-ccwf (GitHub-reviewed advisory GHSA-jxg5-35fj-ccwf lists affected ranges: Packagist typo3/cms-extbase >=0 =7.0 =8.1.1 <=8.1.1)

Commands are suggestions: review each one before running it.

Loading voting…