CVE-2026-92592 craftcms CVE debrief

Who should care

Defenders responsible for Craft CMS installations, particularly those with user accounts using password authentication without active 2FA, should assess exposure and apply patches. System administrators and security teams should verify configurations and monitor for suspicious activity.

Why it matters

CVE-2026-92592 is a high-severity vulnerability in Craft CMS that allows an authenticated, non-administrator user to execute arbitrary operating-system commands as the web-server user. Defenders should prioritize verifying exposure and applying patches, as exploitation requires an account with password authentication and default request configuration.

• Execution of arbitrary operating-system commands as the web-server user
• Potential for lateral movement and escalation of privileges
• Need for verification of exposure and application of patches
• Importance of enforcing strong authentication and 2FA for all users

Technical summary

The vulnerability arises from Craft CMS's use of the same key and format for signing authenticated user license-shun cookies and redirect parameters. An attacker can set a malicious cookie and use it to execute arbitrary operating-system commands as the web-server user by transplanting the signed envelope into the redirect parameter. This issue allows an authenticated, non-administrator user to execute arbitrary operating-system commands as the web-server user, given an account with password authentication and default request configuration.

Defensive priority

Defenders should prioritize verifying exposure and applying patches, as exploitation requires an account with password authentication and default request configuration.

Recommended defensive actions

• Verify exposure by checking Craft CMS versions and configurations
• Apply patches to affected versions (4.18.6 and 5.10.13)
• Restrict access to sensitive endpoints and monitor for suspicious activity
• Enforce strong authentication and 2FA for all users
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, including its description, CVSS score, and affected versions. However, the corpus does not establish versions, exploitation, impact, or remediation beyond vendor-provided information.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.