Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Unrated

TYPO3 Remote File Disclosure vulnerability in the jumpUrl mechanism

CVE-2010-3714GHSA-w736-qv86-vq94

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (typo3/cms 4.4.4, 4.3.7, 4.2.15), 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
    >= 4.2.0, < 4.2.15>= 4.3.0, < 4.3.7>= 4.4.0, < 4.4.4
    Fixed in
    4.2.15, 4.4.4, 4.3.7

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
not scored
EPSS
  • CVE-2010-3714: 24.13% estimated exploitation activity in the next 30 days; percentile 97.85 (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 (aka access tracking) implementation in tslib/class.tslibfe.php in TYPO3 4.2.x before 4.2.15, 4.3.x before 4.3.7, and 4.4.x before 4.4.4 does not properly compare certain hash values during access-control decisions, which allows remote attackers to read arbitrary files via unspecified vectors.

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

    Published from ghsa record GHSA-w736-qv86-vq94

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-2010-3714

Advisory: TYPO3 Remote File Disclosure vulnerability in the jumpUrl mechanism
IDs: CVE-2010-3714, GHSA-w736-qv86-vq94
Record: https://patchnext.com/advisories/cve-2010-3714 (revision 1, source checked 26 Oct 2026, 14:16 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Unrated
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.4.4, 4.3.7, 4.2.15. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist typo3/cms: affected >= 4.2.0, < 4.2.15; >= 4.3.0, < 4.3.7; >= 4.4.0, < 4.4.4; fixed in 4.2.15, 4.4.4, 4.3.7

## 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-w736-qv86-vq94 (GitHub-reviewed advisory GHSA-w736-qv86-vq94 lists affected ranges: Packagist typo3/cms >=4.2.0 =4.3.0 =4.4.0 <4.4.4)

Commands are suggestions: review each one before running it.

Loading voting…