Craft CMS has Stored XSS in Table Field in its "Row Heading" Column Type

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

2.3 · CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N · score source

EPSS

• CVE-2026-56383: 0.22% estimated exploitation activity in the next 30 days; percentile 12.31 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

A stored Cross-site Scripting (XSS) vulnerability exists in the editableTable.twig component when using the Row Heading column type. The application fails to sanitize input within row headings, allowing an attacker to execute arbitrary JavaScript when another user views a page with the malicious table field. Prerequisites An administrator account allowAdminChanges must be enabled in production, which is against security recommendations. Steps to Reproduce 1. Navigate to Settings → Fields and create a new field with Type: Table 1. Add a Column Heading and set Column Type to Row Heading 1. In Default Values section, add a row with the following payload: 1. Enable Static Rows 1. Use the field in any object (e.g., user profile fields) → then visit any user’s profile 1. Notice the XSS execution Resources https://github.com/craftcms/cms/commit/7b372de262b8d9d2ce859f32780c3715719b6f5a

Published by the source

25 Feb 2026, 19:11 UTC

Last modified by the source

6 Aug 2026, 20:47 UTC

Source last checked

26 Oct 2026, 14:50 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-6j87-m5qx-9fqp

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-56383

Advisory: Craft CMS has Stored XSS in Table Field in its "Row Heading" Column Type
IDs: CVE-2026-56383, GHSA-6j87-m5qx-9fqp
Record: https://patchnext.com/advisories/cve-2026-56383 (revision 1, source checked 26 Oct 2026, 14:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 2.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: craftcms/cms 5.8.23, 4.16.19. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist craftcms/cms: affected >= 4.5.0-beta.1, <= 4.16.18; >= 5.0.0-RC1, <= 5.8.22; fixed in 5.8.23, 4.16.19

## Suggested inspection (read-only)
- Packagist craftcms/cms: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on craftcms/cms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-6j87-m5qx-9fqp (GitHub-reviewed advisory GHSA-6j87-m5qx-9fqp lists affected ranges: Packagist craftcms/cms >=4.5.0-beta.1 =5.0.0-RC1 <=5.8.22)

Commands are suggestions: review each one before running it.