Vulnerability advisory

GHSA-7733-hjv6-4h47

Cross-Site Scripting in ternary conditional operator

Published Updated OSV record ↗

Also known as BIT-typo3-2020-15241CVE-2020-15241

Severity
  • CVSS 3.xCVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:L/I:L/A:N

Affected versions

AffectedFixed in
2.0.0 to before 2.0.52.0.5Advisories →
Also listed as affected (5)
2.1.0 to before 2.1.42.1.4Advisories →
Also listed as affected (4)
2.2.0 to before 2.2.12.2.1Advisories →
Also listed as affected (1)
2.3.0 to before 2.3.52.3.5Advisories →
Also listed as affected (5)
2.4.0 to before 2.4.12.4.1Advisories →
Also listed as affected (1)
2.5.0 to before 2.5.52.5.5Advisories →
Also listed as affected (5)
2.6.0 to before 2.6.12.6.1Advisories →
Also listed as affected (1)

Description

Meta
  • CVSS: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N/E:F/RL:O/RC:C(5.0)
  • CWE-79

:information_source:  This vulnerability has been fixed in May 2019 already, CVE and GHSA were assigned later in October 2020


Problem

It has been discovered that the Fluid Engine (package typo3fluid/fluid) is vulnerable to cross-site scripting when making use of the ternary conditional operator in templates like the following.

{showFullName ? fullName : defaultValue}
Solution

Update to versions 2.0.5, 2.1.4, 2.2.1, 2.3.5, 2.4.1, 2.5.5 or 2.6.1 of this typo3fluid/fluid package that fix the problem described.

Updated versions of this package are bundled in following TYPO3 (typo3/cms-core) releases:

  • TYPO3 v8.7.25 (using typo3fluid/fluid v2.5.5)
  • TYPO3 v9.5.6 (using typo3fluid/fluid v2.6.1)
Credits

Thanks to Bill Dagou who reported this issue and to TYPO3 core merger Claus Due who fixed the issue.

References

References

  • Codex
  • Claude Code
  • VS Code
  • GitHub Copilot
  • Cursor
  • Cline
  • Windsurf
  • Google Anti-gravity
  • OpenCode
  • Pi
  • Gemini CLI
  • Hermes Agent
  • Zed
  • Junie
  • Qwen Code
  • Kiro
  • Kilo Code
  • Factory Droid

Set up GitHits for your agents

Run this command:

<> bash
npx githits@latest init

What happens next:

  1. Opens your browser to authorize GitHits
  2. Asks whether to set up GitHits at the user or project level
  3. Detects your supported AI coding tools
  4. Lets you choose which tools to configure
  5. Configures the selected tools