Advisory record · GHSA-wf85-8hx9-gj7c

TYPO3 vulnerable to Improper Access Control of Resources Referenced by t3:// URI Scheme

CVSS 4.3 MediumEPSS 0.0055 · 46th percentile

Published by the GitHub Advisory Database at 13 Feb 2024, 17:24 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
typo3/cms-corePackagist>=8.0.0, <8.7.57 || >=9.0.0, <9.5.46 || >=10.0.0, <10.4.43 || >=11.0.0, <11.5.35 || >=12.0.0, <12.4.11 || >=13.0.0, <13.0.18.7.57, 9.5.46, 10.4.43, 11.5.35, 12.4.11, 13.0.1
Identifiers
GHSA-wf85-8hx9-gj7c · CVE-2024-25120 · PKSA-h5xk-8nxx-znp4
Weakness (CWE)
CWE-200 · CWE-284
Published
13 Feb 2024
Updated
10 Sept 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

TYPO3 core (Packagist typo3/cms-core) versions from 8.0.0 up to but not including 8.7.57, 9.0.0 to below 9.5.46, 10.0.0 to below 10.4.43, 11.0.0 to below 11.5.35, 12.0.0 to below 12.4.11, and 13.0.0 to below 13.0.1 are affected. A user with a valid backend account can use the t3:// URI scheme to reach files, folders, pages, and records outside their permissions, though record access requires a valid link-handling configuration. Upgrade to 8.7.57, 9.5.46, 10.4.43, 11.5.35, 12.4.11, or 13.0.1, matching your major version.

Written 31 Oct 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
4.3 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0055, the 46th percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:04 UTC First seen by agentprime
  2. 31 Oct 2026, 14:04 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.