Skip to main content
VulnerabilityPublished Updated

CVE-2026-33051: craftcms cms · Cross-site Scripting

Affects craftcms cmsSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.3 Medium : upgrade to 5.9.11 when convenient.

Data as of 31 Oct 2026, 20:20 UTC

CVSS 4.0 base score
5.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 16% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 5.9.11
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 20 Mar 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 31 Oct 2026.

What to do

Upgrade craftcms cms to 5.9.11.

Affected software

ProductAffectedFixed in
craftcmscmsAffected
  • >=5.9.0-beta.1 <5.9.11
Fixed in
  • 5.9.11

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

Organizations should immediately upgrade Craft CMS installations to version 5.9.11 or later, where the vulnerability is patched. Until upgrade is possible, restrict low-privileged user capabilities to prevent profile modifications that include HTML or script content in the fullName field. Implement strict input validation and sanitization on user profile fields to block injection of HTML or JavaScript. Monitor logs for suspicious profile changes or repeated entry saves by low-privileged users. Limit concurrent administrative sessions and consider implementing multi-factor authentication (MFA) for admin accounts to reduce risk of session hijacking. Employ Content Security Policy (CSP) headers to mitigate impact of potential XSS payloads. Conduct regular audits of user roles and permissions to ensure minimal necessary privileges. Educate administrators to log out when not actively managing the CMS to reduce exposure window. Finally, maintain up-to-date backups to recover from potential compromises.

Description

Craft CMS is a content management system (CMS). In versions 5.9.0-beta.1 through 5.9.10, the revision/draft context menu in the element editor renders the creator’s fullName as raw HTML due to the use of Template::raw() combined with Craft::t() string interpolation. A low-privileged control panel user (e.g., Author) can set their fullName to an XSS payload via the profile editor, then create an entry with two saves. If an administrator is logged in and executes a specifically crafted payload while an elevated session is active, the attacker’s account can be elevated to administrator. This issue has been fixed in version 5.9.11.

References

Community reviews

Loading reviews…