Advisory record · GHSA-qx3w-4864-94ch

Cleartext storage of session identifier

CVSS 5.9 MediumEPSS 0.0092 · 61st percentile

Published by the GitHub Advisory Database at 23 Mar 2021, 01:53 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
typo3/cms-corePackagist>=6.2.0, <6.2.57 || >=7.0.0, <7.6.51 || >=8.0.0, <8.7.40 || >=10.0.0, <10.4.14 || >=11.0.0, <11.1.1 || >=9.0.0, <9.5.256.2.57, 7.6.51, 8.7.40, 10.4.14, 11.1.1, 9.5.25
typo3/cmsPackagist>=10.0.0, <10.4.14 || >=11.0.0, <11.1.1 || >=9.0.0, <9.5.2510.4.14, 11.1.1, 9.5.25
Identifiers
GHSA-qx3w-4864-94ch · BIT-typo3-2021-21339 · CVE-2021-21339 · PKSA-6rj9-2kkd-njb3 · PKSA-k7qq-jvk9-4s56
Weakness (CWE)
CWE-312
Published
23 Mar 2021
Updated
8 Jul 2026

Machine-written summary

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

Two TYPO3 packages are affected: typo3/cms-core (versions before 6.2.57, 7.6.51, 8.7.40, 9.5.25, 10.4.14 and 11.1.1 in their respective branches) and typo3/cms (versions before 9.5.25, 10.4.14 and 11.1.1). Session identifiers are stored in cleartext, and the source says this cannot be exploited directly but only in combination with a chained attack such as SQL injection in another component. Upgrade to the fixed versions listed for your branch.

Written 3 Nov 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
5.9 Medium 3.1 CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0092, the 61st percentile, on 20 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:25 UTC First seen by agentprime
  2. 31 Oct 2026, 14:25 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.