XSS in richtext custom tag attributes in ezsystems/ezplatform-richtext
The advisory, in context
The rich text editor does not escape attribute data when previewing custom tags. This means XSS is possible if custom tags are used, for users who have access to editing rich text content. Frontend content view is not affected, but the vulnerability could be used by editors to attack other editors. The fix ensures custom tag attribute data is escaped in the editor.
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.
From 1.5.0 before 1.5.25.1
Fixed in 1.5.25.1
28 explicitly affected versions
v1.5.0, v1.5.1, v1.5.10, v1.5.11, v1.5.12, v1.5.13, v1.5.14, v1.5.15, v1.5.16, v1.5.17, v1.5.18, v1.5.19, v1.5.2, v1.5.20, v1.5.21, v1.5.22, v1.5.23, v1.5.24, v1.5.25, v1.5.3, v1.5.4, v1.5.5, v1.5.6, v1.5.7, v1.5.8, v1.5.8-rc1, v1.5.9, v1.5.9-rc1
View affected-version evidence
{
"ranges": [
{
"events": [
{
"introduced": "1.5.0"
},
{
"fixed": "1.5.25.1"
}
],
"type": "ECOSYSTEM"
}
],
"versions": [
"v1.5.0",
"v1.5.1",
"v1.5.10",
"v1.5.11",
"v1.5.12",
"v1.5.13",
"v1.5.14",
"v1.5.15",
"v1.5.16",
"v1.5.17",
"v1.5.18",
"v1.5.19",
"v1.5.2",
"v1.5.20",
"v1.5.21",
"v1.5.22",
"v1.5.23",
"v1.5.24",
"v1.5.25",
"v1.5.3",
"v1.5.4",
"v1.5.5",
"v1.5.6",
"v1.5.7",
"v1.5.8",
"v1.5.8-rc1",
"v1.5.9",
"v1.5.9-rc1"
]
}