CSRF token exposure in TYPO3 extension

published 2021-08-13 5y ago modified 2026-06-17 4mo ago also GHSA-vpw5-grxx-v396 , EUVD-2021-2116

cvss: 7.5; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 1.0%; EPSS 1.0% chance of exploitation in 30 days, percentile 63%
public exploits: 0; none known

The routes (aka Extbase Yaml Routes) extension before 2.1.1 for TYPO3, when CsrfTokenViewHelper is used, allows Sensitive Information Disclosure because a session identifier is unsafely present in HTML output.

Patch / fix

fixed in 2

packagist lms/routes 2.1.1
routes_project routes 2.1.1

Is CVE-2021-36793 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Exploit prediction

1.01% chance of exploitation in the next 30 days, higher than 63% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by	version	score	vector
NVD	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:P/I:N/A:N
GitHub	3.1	6.8	CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N/E:F/RL:O/RC:C

Affected packages

ecosystem	package	affected	fixed in
packagist	lms/routes	<2.1.1	2.1.1

Classification

Weakness

CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
CWE-668 Exposure of Resource to Wrong Sphere

References

typo3.org /help/security-advisories/security
vendor-advisory
typo3.org /security/advisory/typo3-ext-sa-2021-008
web, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2021-36793
advisory
github.com /Lacr1ma/routes
package

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.