Breaking News: Thousands Of GitHub Accounts Hijacked With wfx-loot CI Secret
Read the Report
Learn How MCP Is Bypassing a Decade of Cloud Security Best Practices
Read the Report
Are you exposed? Connect a repo in minutes.
Scan your repos free

typo3fluid/fluid

Composer (PHP) package

Overview

Newest range
2.6.10
Last CVE
17 Nov 2020
Composer (PHP) 22 version ranges 14 affected
0 Critical
0 High
2 Medium
0 Low

Package versions

Version ranges and their known vulnerabilities
VersionsRangeDirect vulnerabilities
2.6.10 and later versions 0000
2.6.1 up to 2.6.10 0010
2.6.0 up to 2.6.1 0020
2.5.11 up to 2.6.0 0000
2.5.5 up to 2.5.11 0010
2.5.0 up to 2.5.5 0020
2.4.4 up to 2.5.0 0000
2.4.1 up to 2.4.4 0010
2.4.0 up to 2.4.1 0020
2.3.7 up to 2.4.0 0000
2.3.5 up to 2.3.7 0010
2.3.0 up to 2.3.5 0020
2.2.4 up to 2.3.0 0000
2.2.1 up to 2.2.4 0010
2.2.0 up to 2.2.1 0020
2.1.7 up to 2.2.0 0000
2.1.4 up to 2.1.7 0010
2.1.0 up to 2.1.4 0020
2.0.8 up to 2.1.0 0000
2.0.5 up to 2.0.8 0010
2.0.0 up to 2.0.5 0020
before 2.0.0 all earlier versions 0000

No known vulnerabilities in 2.6.10 and later versions

Nothing in our data affects this version.

22 ranges in total. Each row is a range of versions with the same vulnerabilities, newest first. The data names only the versions where something changes (first affected, fixed), so the versions in between are a range.

Vulnerabilities · 2

Known vulnerabilities of this package
CVESeverityPublishedVulnerableFixed in
CVE-2020-26216Cross-Site Scripting through Fluid view helper arguments MEDIUM 17 Nov 2020 >=2.0.0, <2.0.8>=2.1.0, <2.1.7>=2.2.0, <2.2.4>=2.3.0, <2.3.7>=2.4.0, <2.4.4>=2.5.0, <2.5.11>=2.6.0, <2.6.10 2.0.82.1.72.2.42.3.72.4.42.5.112.6.10
CVE-2020-15241Cross-Site Scripting in Fluid Engine MEDIUM 8 Oct 2020 >=2.0.0, <2.0.5>=2.1.0, <2.1.4>=2.2.0, <2.2.1>=2.3.0, <2.3.5>=2.4.0, <2.4.1>=2.5.0, <2.5.5>=2.6.0, <2.6.1 2.0.52.1.42.2.12.3.52.4.12.5.52.6.1

OX Radar and Response Center

Find threats in your stack.

OX Radar can check high-priority threats, like critical package CVEs, against your context.

Each incident is marked Detected or Not Detected with a remediation plan and proof all tracked in the Response Center.