Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9

TYPO3 leaks a hash secret in an error message

CVE-2009-0815GHSA-c22j-84c7-cm77

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (typo3/cms 4.2.6, 4.1.10, 4.0.12), 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
    >= 3.3, < 4.0.12>= 4.1, < 4.1.10>= 4.2, < 4.2.6
    Fixed in
    4.1.10, 4.2.6, 4.0.12

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2009-0815: 42.23% estimated exploitation activity in the next 30 days; percentile 98.70 (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.

The jumpUrl mechanism in class.tslibfe.php in TYPO3 3.3.x through 3.8.x, 4.0 before 4.0.12, 4.1 before 4.1.10, 4.2 before 4.2.6, and 4.3alpha1 leaks a hash secret (juHash) in an error message, which allows remote attackers to read arbitrary files by including the hash in a request.

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

    Published from ghsa record GHSA-c22j-84c7-cm77

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-2009-0815

Advisory: TYPO3 leaks a hash secret in an error message
IDs: CVE-2009-0815, GHSA-c22j-84c7-cm77
Record: https://patchnext.com/advisories/cve-2009-0815 (revision 1, source checked 26 Oct 2026, 14:30 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: typo3/cms 4.2.6, 4.1.10, 4.0.12. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms: affected >= 3.3, < 4.0.12; >= 4.1, < 4.1.10; >= 4.2, < 4.2.6; fixed in 4.1.10, 4.2.6, 4.0.12

## 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-c22j-84c7-cm77 (GitHub-reviewed advisory GHSA-c22j-84c7-cm77 lists affected ranges: Packagist typo3/cms >=3.3 =4.1 =4.2 <4.2.6)

Commands are suggestions: review each one before running it.

Loading voting…