How severe is GHSA-24x4-j6x9-rfw5?

No CVSS score has been assigned to GHSA-24x4-j6x9-rfw5 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-24x4-j6x9-rfw5?

GHSA-24x4-j6x9-rfw5 affects the following packages: craftcms/cms (Packagist), craftcms/cms (Packagist). Ecosystems affected: Packagist.

How do I fix GHSA-24x4-j6x9-rfw5?

Update craftcms/cms to 5.9.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-24x4-j6x9-rfw5 is resolved across your whole dependency graph.

How do I detect GHSA-24x4-j6x9-rfw5 in my Packagist dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/cms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-24x4-j6x9-rfw5 if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-24x4-j6x9-rfw5?

O3 pinpoints whether GHSA-24x4-j6x9-rfw5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-24x4-j6x9-rfw5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-24x4-j6x9-rfw5 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-24x4-j6x9-rfw5?

GHSA-24x4-j6x9-rfw5 is classified as Cross-site Scripting (XSS) (CWE-79). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

When was GHSA-24x4-j6x9-rfw5 published, and has it been updated?

GHSA-24x4-j6x9-rfw5 was published on July 6, 2026 and was last updated on July 6, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐘 Packagist

Not in CISA KEV

GHSA-24x4-j6x9-rfw5

Fix: craftcms/cms@6bbb660

GHSA-24x4-j6x9-rfw5 is a Cross-site Scripting (XSS) vulnerability in craftcms/cms. O3 Security confirms whether GHSA-24x4-j6x9-rfw5 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Craft CMS: DOM XSS via GitHub issue title in CraftSupport widget

Also known asCVE-2026-55790

Published

Jul 6, 2026

Updated

Jul 6, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Exploitation data as of Jul 6, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

2 pkgs affected

🐘craftcms/cms🐘craftcms/cms

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Packagist packages — download data is not available via public APIs for these ecosystems.

Description

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

Attacker has a GitHub account (no control panel access needed).
Victim is an administrator, and you have the CraftSupport widget on the dashboard.
Victim uses the "Give feedback" screen and types a search term that returns the poisoned issue.

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):

Open https://github.com/craftcms/cms/issues/new.
Set the title to a string combining a plausible search term and the payload, e.g.:

<img src=x onerror=alert(document.domain)> cannot upload files

Submit the issue.

Trigger (victim, Craft admin):

Open the Craft control panel dashboard.
Open the CraftSupport widget, click "Give feedback".
Type 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

Victim must actively use the "Give feedback" search screen.
Attacker must predict or social-engineer a search term the admin will type, or use a broad term likely to match.
Widget is only available to admins.

Resources

https://github.com/craftcms/cms/commit/6bbb66038a268552180ca5c8eed9f46ea25a4417

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐘Packagist	`craftcms/cms`	≥ 5.0.0-RC1&&< 5.9.23	5.9.23
🐘Packagist	`craftcms/cms`	≥ 4.0.0-RC1&&< 4.17.16	4.17.16

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for craftcms/cms. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update craftcms/cms to 5.9.23 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-24x4-j6x9-rfw5 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-24x4-j6x9-rfw5 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-24x4-j6x9-rfw5. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

## 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 - Attacker has a GitHub account (no control panel access needed). - Victim is an administrator, and you have the CraftSupport widget on the dashboard. - Victim uses the "Give feedback" screen

O3 Security · Impact-Aware SCA

Is GHSA-24x4-j6x9-rfw5 in your dependencies?

O3 detects GHSA-24x4-j6x9-rfw5 across Packagist dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works