CVE-2026-55793 Craft CMS: Stored XSS via Structure entry title in table view
An author can inject JavaScript into entry titles, which executes in admin sessions during drag-and-drop operations in the control panel.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- A user has to click or open something
- Fix
- Available
What is CVE-2026-55793?
CVE-2026-55793 is a medium-severity cross-site scripting vulnerability in craftcms cms, published on 1 Jul 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Official description
Craft CMS is a content management system (CMS). In versions 5.0.0-RC1 through 5.9.22, an author-level control panel user can store a malicious JavaScript payload in an entry title. When an admin, or any control panel user with saveEntries for the same Structure section, drags another entry under the poisoned entry in table view, the payload executes in the victim’s session. The issue is exploitable because the title is escaped into data-title by the server, decoded again by the browser, read with jQuery .data('title'), and then concatenated into a new HTML string without attribute escaping. To exploit, an attacker must have an existing control panel account (Author role minimum), the victim must perform a drag operation (not just visit the page), and the victim’s session needs to be elevated at trigger time. This issue has been fixed in version 5.9.23.
Weakness: CWE-79
Which versions are affected by CVE-2026-55793?
2 open source packages ship an affected version, including craftcms/cms.
| Package | Affected | Fixed in |
|---|---|---|
craftcms/cms Packagist | From 5.0.0-RC1 | 5.9.53 |
craftcms/cms Packagist | From 5.0.0-RC1 | 5.9.53 |
How do I fix CVE-2026-55793?
Upgrade craftcms/cms to 5.9.53 or later.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-55793 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-55793 exists.
Sources
Also known as CLSA-2026-1789415531, GHSA-xrqc-p465-2xvg.