Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2020-26216

Cross-Site Scripting (XSS) in typo3fluid/fluid (CVE-2020-26216)

Summary

Cross-site scripting in typo3fluid/fluid (CVE-2020-26216). Confidential information can be exposed externally. Exploitable via additionalAttributes. Mitigation: upgrade to 2.6.10 or later.

Original description

The description as published by the source.

Meta

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

Problem

Three XSS vulnerabilities have been detected in Fluid:

  1. TagBasedViewHelper allowed XSS throug maliciously crafted additionalAttributes arrays by creating keys with attribute-closing quotes followed by HTML. When rendering such attributes, TagBuilder would not escape the keys.
  2. ViewHelpers which used the CompileWithContentArgumentAndRenderStatic trait, and which declared escapeOutput = false, would receive the content argument in unescaped format.
  3. Subclasses of AbstractConditionViewHelper would receive the then and else arguments in unescaped format.

Solution

Update to versions 2.0.8, 2.1.7, 2.2.4, 2.3.7, 2.4.4, 2.5.11 or 2.6.10 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 v9.5.23 (using typo3fluid/fluid v2.6.10)
  • TYPO3 v10.4.10 (using typo3fluid/fluid v2.6.10)

The specific vulnerabilities are prevented by:

  1. Explicitly escaping keys found in the additionalAttributes array passed to a TagBasedViewHelper before using them as attribute names.
  2. Detecting "content argument" on ViewHelpers using the trait CompileWithContentArgumentAndRenderStatic and escaping it based on the state of escapeChildren when escapeOutput is toggled off. Escaping still will not occur if explicitly disabled by an enclosing ViewHelper. Th…

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2020-26216 has been found in typo3fluid/fluid.
Attackers can target a specific entry point like additionalAttributes over the network to misuse the product.
Confidential information can be exposed externally.
What to do: upgrade typo3fluid/fluid to 2.6.10 or later.
If unsure, ask your IT team or search "typo3fluid/fluid CVE-2020-26216" on the vendor's site.

CVE-2020-26216 (typo3fluid/fluid) — CWE-79
Attack vector: remote (network-reachable) / unauthenticated
Attack surface: additionalAttributes / CompileWithContentArgumentAndRenderStatic / then / else
Patched: 2.6.10 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Cross-site scripting (XSS) (CWE-79) exists in typo3fluid/fluid. Attackers reach the vulnerable code path via additionalAttributes without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of typo3fluid/fluid. Attack surface: additionalAttributes / CompileWithContentArgumentAndRenderStatic / then / else.

🔥 Severity

Severity: ?. Confidential information can be exposed externally.

🔧 How to fix

Update to 2.6.10.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'typo3fluid/fluid' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'typo3fluid/fluid' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で typo3fluid/fluid を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade typo3fluid/fluid to 2.6.10

    ステージング環境で 2.6.10 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Packagist typo3fluid/fluid
[{"type":"ECOSYSTEM","events":[{"introduced":"2.6.0"},{"fixed":"2.6.10"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details