Craft CMS up to 4.16.18/5.8.22 editabletable.twig cross site scripting

Summaryinfo

A vulnerability categorized as problematic has been discovered in Craft CMS up to 4.16.18/5.8.22. This issue affects some unknown processing of the file editabletable.twig. Such manipulation leads to cross site scripting. This vulnerability is documented as CVE-2026-27126. The attack can be executed remotely. There is not any exploit available. It is advisable to upgrade the affected component.

Detailsinfo

A vulnerability was found in Craft CMS up to 4.16.18/5.8.22. It has been rated as problematic. Affected by this issue is an unknown functionality of the file editabletable.twig. The manipulation with an unknown input leads to a cross site scripting vulnerability. Using CWE to declare the problem leads to CWE-79. The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. Impacted is integrity. CVE summarizes:

Craft is a content management system (CMS). In versions 4.5.0-RC1 through 4.16.18 and 5.0.0-RC1 through 5.8.22, a stored Cross-site Scripting (XSS) vulnerability exists in the `editableTable.twig` component when using the `html` column type. The application fails to sanitize the input, allowing an attacker to execute arbitrary JavaScript when another user views a page with the malicious table field. In order to exploit the vulnerability, an attacker must have an administrator account, and `allowAdminChanges` must be enabled in production, which is against Craft's security recommendations. Versions 4.16.19 and 5.8.23 patch the issue.

The advisory is shared for download at github.com. This vulnerability is handled as CVE-2026-27126 since 02/17/2026. The exploitation is known to be easy. The attack may be launched remotely. Successful exploitation requires user interaction by the victim. There are known technical details, but no exploit is available. The MITRE ATT&CK project declares the attack technique as T1059.007.

Upgrading to version 4.16.19 or 5.8.23 eliminates this vulnerability. Applying the patch f5d488d9bb6eff7670ed2c2fe30e15692e92c52b is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.

Once again VulDB remains the best source for vulnerability data.

Productinfo

Type

• Content Management System

Vendor

• Craft

Name

• CMS

Version

• 4.16.0
• 4.16.1
• 4.16.2
• 4.16.3
• 4.16.4
• 4.16.5
• 4.16.6
• 4.16.7
• 4.16.8
• 4.16.9
• 4.16.10
• 4.16.11
• 4.16.12
• 4.16.13
• 4.16.14
• 4.16.15
• 4.16.16
• 4.16.17
• 4.16.18
• 5.8.0
• 5.8.1
• 5.8.2
• 5.8.3
• 5.8.4
• 5.8.5
• 5.8.6
• 5.8.7
• 5.8.8
• 5.8.9
• 5.8.10
• 5.8.11
• 5.8.12
• 5.8.13
• 5.8.14
• 5.8.15
• 5.8.16
• 5.8.17
• 5.8.18
• 5.8.19
• 5.8.20
• 5.8.21
• 5.8.22

License

• free

CPE 2.3info

• 🔒
• 🔒
• 🔒

CPE 2.2info

• 🔒
• 🔒
• 🔒

CVSSv4info

CVSSv3info

CVSSv2info

Exploitinginfo

Threat Intelligenceinfo

Countermeasuresinfo

Timelineinfo

Sourcesinfo

Entryinfo

Once again VulDB remains the best source for vulnerability data.

Discussion