GIVE YOUR AGENT THE EVIDENCE

Set up in your agent.

One prompt to get started. Paste it into your coding agent to connect cve.new through MCP and bring vulnerability context into your workflow.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

GIVE YOUR AGENT THE EVIDENCE

Investigate in your agent.

Turn this advisory into a focused investigation. Ask your agent to check your project’s versions, explain the evidence, and suggest a compatible fix.

Your agent needs remote MCP support and access to https://cve.new/mcp.

Read the setup guide

cve.new
GHSA-hvwx-qh2h-xcfjmedium6.1

TYPO3 HTML Sanitizer vulnerable to Cross-Site Scripting

Check your stack

The advisory, in context

Problem

Due to a parsing issue in the upstream package masterminds/html5, malicious markup used in a sequence with special HTML CDATA sections cannot be filtered and sanitized. This allows bypassing the cross-site scripting mechanism of typo3/html-sanitizer.

Besides that, the upstream package masterminds/html5 provides HTML raw text elements (script, style, noframes, noembed and iframe) as DOMText nodes, which were not processed and sanitized further. None of the mentioned elements were defined in the default builder configuration, that's why only custom behaviors, using one of those tag names, were vulnerable to cross-site scripting.

Solution

Update to typo3/html-sanitizer versions 1.5.0 or 2.1.1 that fix the problem described.

Affected packages

Start with the recorded fix for your release branch. Check your installed version and test compatibility before upgrading. Fixing this advisory does not rule out other vulnerabilities in the release.

Ecosystem versions

From 1.0.0 before 1.5.0

Fixed in 1.5.0

8 explicitly affected versions

v1.0.0, v1.0.1, v1.0.2, v1.0.3, v1.0.4, v1.0.5, v1.0.6, v1.0.7

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "1.0.0"
        },
        {
          "fixed": "1.5.0"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v1.0.0",
    "v1.0.1",
    "v1.0.2",
    "v1.0.3",
    "v1.0.4",
    "v1.0.5",
    "v1.0.6",
    "v1.0.7"
  ]
}
Ecosystem versions

From 2.0.0 before 2.1.1

Fixed in 2.1.1

18 explicitly affected versions

v2.0.0, v2.0.1, v2.0.10, v2.0.11, v2.0.12, v2.0.13, v2.0.14, v2.0.15, v2.0.16, v2.0.2, v2.0.3, v2.0.4, v2.0.5, v2.0.6, v2.0.7, v2.0.8, v2.0.9, v2.1.0

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "2.0.0"
        },
        {
          "fixed": "2.1.1"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v2.0.0",
    "v2.0.1",
    "v2.0.10",
    "v2.0.11",
    "v2.0.12",
    "v2.0.13",
    "v2.0.14",
    "v2.0.15",
    "v2.0.16",
    "v2.0.2",
    "v2.0.3",
    "v2.0.4",
    "v2.0.5",
    "v2.0.6",
    "v2.0.7",
    "v2.0.8",
    "v2.0.9",
    "v2.1.0"
  ]
}
typo3/cms Packagist
Ecosystem versions

From 10.0.0 before 10.4.33

Fixed in 10.4.33

39 explicitly affected versions

v10.0.0, v10.1.0, v10.2.0, v10.2.1, v10.2.2, v10.3.0, v10.4.0, v10.4.1, v10.4.10, v10.4.11, v10.4.12, v10.4.13, v10.4.14, v10.4.15, v10.4.16, v10.4.17, v10.4.18, v10.4.19, v10.4.2, v10.4.20, v10.4.21, v10.4.22, v10.4.23, v10.4.24, v10.4.25, v10.4.26, v10.4.27, v10.4.28, v10.4.29, v10.4.3, v10.4.30, v10.4.31, v10.4.32, v10.4.4, v10.4.5, v10.4.6, v10.4.7, v10.4.8, v10.4.9

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "10.0.0"
        },
        {
          "fixed": "10.4.33"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v10.0.0",
    "v10.1.0",
    "v10.2.0",
    "v10.2.1",
    "v10.2.2",
    "v10.3.0",
    "v10.4.0",
    "v10.4.1",
    "v10.4.10",
    "v10.4.11",
    "v10.4.12",
    "v10.4.13",
    "v10.4.14",
    "v10.4.15",
    "v10.4.16",
    "v10.4.17",
    "v10.4.18",
    "v10.4.19",
    "v10.4.2",
    "v10.4.20",
    "v10.4.21",
    "v10.4.22",
    "v10.4.23",
    "v10.4.24",
    "v10.4.25",
    "v10.4.26",
    "v10.4.27",
    "v10.4.28",
    "v10.4.29",
    "v10.4.3",
    "v10.4.30",
    "v10.4.31",
    "v10.4.32",
    "v10.4.4",
    "v10.4.5",
    "v10.4.6",
    "v10.4.7",
    "v10.4.8",
    "v10.4.9"
  ]
}
typo3/cms Packagist
Ecosystem versions

From 11.0.0 before 11.5.20

Fixed in 11.5.20

29 explicitly affected versions

v11.0.0, v11.1.0, v11.1.1, v11.2.0, v11.3.0, v11.3.1, v11.3.2, v11.3.3, v11.4.0, v11.5.0, v11.5.1, v11.5.10, v11.5.11, v11.5.12, v11.5.13, v11.5.14, v11.5.15, v11.5.16, v11.5.17, v11.5.18, v11.5.19, v11.5.2, v11.5.3, v11.5.4, v11.5.5, v11.5.6, v11.5.7, v11.5.8, v11.5.9

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "11.0.0"
        },
        {
          "fixed": "11.5.20"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v11.0.0",
    "v11.1.0",
    "v11.1.1",
    "v11.2.0",
    "v11.3.0",
    "v11.3.1",
    "v11.3.2",
    "v11.3.3",
    "v11.4.0",
    "v11.5.0",
    "v11.5.1",
    "v11.5.10",
    "v11.5.11",
    "v11.5.12",
    "v11.5.13",
    "v11.5.14",
    "v11.5.15",
    "v11.5.16",
    "v11.5.17",
    "v11.5.18",
    "v11.5.19",
    "v11.5.2",
    "v11.5.3",
    "v11.5.4",
    "v11.5.5",
    "v11.5.6",
    "v11.5.7",
    "v11.5.8",
    "v11.5.9"
  ]
}
typo3/cms Packagist
Ecosystem versions

From 12.0.0 before 12.1.1

Fixed in 12.1.1

2 explicitly affected versions

v12.0.0, v12.1.0

View affected-version evidence
{
  "ranges": [
    {
      "events": [
        {
          "introduced": "12.0.0"
        },
        {
          "fixed": "12.1.1"
        }
      ],
      "type": "ECOSYSTEM"
    }
  ],
  "versions": [
    "v12.0.0",
    "v12.1.0"
  ]
}

References