craftcms/cms
Affected
- introduced
5.0.0-RC1, fixed5.9.23(ecosystem)
Fixed versions
5.9.23
Fix
The export has no generic command for this ecosystem.
Advisory
Also known as: CVE-2026-55790
Craft CMS: DOM XSS via GitHub issue title in CraftSupport widget
Summary
An attacker with only a GitHub account can plant a JavaScript payload in a craftcms/cms issue title. When a Craft admin uses the CraftSupport widget’s "Give feedback" screen and types a search term that returns the poisoned issue, the payload executes in the admin’s control panel session.
No control panel account or elevated privileges are required on the attacker’s side.
Preconditions
Root cause
CraftSupportWidget.js lines 382-392:
$('<a>', {
href: this.getSearchResultUrl(results[i]),
target: '_blank',
html:
'<span class="status ' +
this.getSearchResultStatus(results[i]) +
'"></span>' +
this.getSearchResultText(results[i]),
})
FeedbackScreen.getSearchResultText (line 669-671) returns result.title verbatim from the GitHub API response. The jQuery html: option sets the element’s innerHTML, so a title containing <img src=x onerror=...> executes immediately on render.
The GitHub API returns issue titles as raw JSON strings with no HTML encoding. The widget makes this request directly from the browser, without a Craft proxy or any sanitization step.
HelpScreen (Stack Exchange) is not affected because the Stack Exchange API HTML-encodes titles before returning them.
Steps to reproduce
Plant (attacker, GitHub account only):
https://github.com/craftcms/cms/issues/new.<img src=x onerror=alert(document.domain)> cannot upload files
Trigger (victim, Craft admin):
cannot upload files in the search box.alert(document.domain) fires in the admin's session.Impact
XSS in the admin control panel session. The payload has access to Craft.csrfTokenName and Craft.csrfTokenValue and can send same-origin action requests as the admin without any further interaction.
Mitigating factors
Resources
https://github.com/craftcms/cms/commit/6bbb66038a268552180ca5c8eed9f46ea25a4417
High Basis: The source's own band: HIGH
5.0.0-RC1, fixed 5.9.23 (ecosystem)5.9.23
The export has no generic command for this ecosystem.
4.0.0-RC1, fixed 4.17.16 (ecosystem)4.17.16
The export has no generic command for this ecosystem.
Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.
Check your own computer: guard packages check
Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0