
Loading

Loading
We use strictly necessary cookies to run this site, and analytics cookies to understand how it's used. See our Privacy Policy for details.
A GitHub-reviewed security advisory, not necessarily under active exploitation the way our CISA KEV advisories are, but a real, disclosed vulnerability in an open-source dependency.
Affected packages
Vulnerable: >= 4.9.0, < 5.3.50
Patched in 5.3.50
Vulnerable: >= 5.4.0-RC1, < 5.7.12
Patched in 5.7.12
Details
Commit 23e8cca3136a hardened the search-result title against insert-tag/XSS by setting $objTemplate->title = StringUtil::specialchars(StringUtil::stripInsertTags($arrResult[$i]['title'])). But the legacy HTML5 template does not use that title variable - it prints the raw link variable, which is assigned without escaping.
Affected configuration (important): on 5.7.9 the default search template is the Twig search_default.html.twig, which does not use the raw link variable and auto-escapes - so a default Twig install is not affected. The vulnerable raw echo is in the legacy search_default.html5 template (still shipped and selectable in 5.7.9, line 8: <?= $this->link ?>); exploitation requires that legacy template to be active for the search module (common on sites migrated from earlier Contao / using custom template selection). Where the legacy template is used, the sink is unambiguously raw and ModuleSearch::compile() assigns link from the entity-decoded indexed title.
A backend page editor can store script that executes for anonymous front-end visitors (and admins) viewing search results, a stored XSS crossing the editor -> anonymous-visitor boundary.
This security vulnerability was found by @HDWSec
More composer advisories
Talk to us about this
Find out whether this dependency (or others like it) is actually reachable in your codebase.
Get help patching, or building dependency-scanning into your pipeline going forward.
A secure code review or supply chain review finds this before an advisory does.