GHSA-7733-hjv6-4h47 is a medium-severity (CVSS 4.7) Open Redirect vulnerability in typo3fluid/fluid. 2 public exploit references exist, so weaponization risk is real. O3 Security confirms whether GHSA-7733-hjv6-4h47 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Cross-Site Scripting in ternary conditional operator
Real-World Exposure
typo3fluid/fluid🐘typo3fluid/fluid🐘typo3fluid/fluid🐘typo3fluid/fluid🐘typo3fluid/fluid🐘typo3fluid/fluid🐘typo3fluid/fluid🐘typo3/cms-core+3 moreReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.
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/fluidv2.5.5) - TYPO3 v9.5.6 (using
typo3fluid/fluidv2.6.1)
Credits
Thanks to Bill Dagou who reported this issue and to TYPO3 core merger Claus Due who fixed the issue.
References
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐘Packagist | typo3fluid/fluid | ≥ 2.0.0&&< 2.0.5 | 2.0.5 |
| 🐘Packagist | typo3fluid/fluid | ≥ 2.1.0&&< 2.1.4 | 2.1.4 |
| 🐘Packagist | typo3fluid/fluid | ≥ 2.2.0&&< 2.2.1 | 2.2.1 |
| 🐘Packagist | typo3fluid/fluid | ≥ 2.3.0&&< 2.3.5 | 2.3.5 |
| 🐘Packagist | typo3fluid/fluid | ≥ 2.4.0&&< 2.4.1 | 2.4.1 |
| 🐘Packagist | typo3fluid/fluid | ≥ 2.5.0&&< 2.5.5 | 2.5.5 |
Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.
Detection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for typo3fluid/fluid. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update typo3fluid/fluid to 2.0.5 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-7733-hjv6-4h47 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-7733-hjv6-4h47 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-7733-hjv6-4h47. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-7733-hjv6-4h47 in your dependencies?
O3 detects GHSA-7733-hjv6-4h47 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.