MediumGHSA-9f5h-mmq6-2x78CVE-2026-25496

Craft CMS Vulnerable to Stored XSS in Number Prefix & Suffix Fields

Published 9 Feb 2026 · Updated 22 Feb 2026

Affected packages

craftcms/cmsComposer
Affected
>=5.0.0-RC1 <5.8.22
Fixed in
5.8.22
Update to the fixed version for your release line, for example:composer require craftcms/cms:^5.8.22
craftcms/cmsComposer
Affected
>=4.0.0-RC1 <4.16.18
Fixed in
4.16.18
Update to the fixed version for your release line, for example:composer require craftcms/cms:^4.16.18

Details

Summary

A stored XSS vulnerability exists in the Number field type settings. The Prefix and Suffix fields are rendered using the |md|raw Twig filter without proper escaping, allowing script execution when the Number field is displayed on users' profiles.

Proof of Concept

Required Permissions

Steps to Reproduce

1. Log in with an admin account 2. Navigate to Settings → Fields → New field 3. Choose Number as the field type 4. Set the Prefix/Suffix Text field to: <img width="611" height="908" alt="image" src="https://github.com/user-attachments/assets/63766ca4-4fa9-490b-8bea-37364137527d" />

<img src=x onerror="alert('Number Prefix/Suffix XSS')" hidden>

5. Save the field 6. Add this field to any element (e.g., User Profile fields via Settings → Users → User Fields) 7. Navigate to your account (/admin/myaccount) or any user profile (/admin/users/{id}) 8. XSS executes when viewing the form <img width="1246" height="677" alt="image-1" src="https://github.com/user-attachments/assets/dafeb2b7-905f-4a4b-b3d6-1c16a905498f" />

Mitigation

Sanitize prefix/suffix before rendering or use |e filter instead of |raw.

Is GHSA-9f5h-mmq6-2x78 in any of your client repos?

Checking one package by hand is fine. Checking it across forty client projects is not. NPMscan reads the lockfiles in every GitHub repo you pick, finds each project with an affected craftcms/cms, and gives you the command that fixes it.

References

Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily.