CVE-2026-14793: Craft CMS Authorization Bypass in Global Sets Reordering
Craft CMS versions up to 4.18.0.1 contain an authorization bypass vulnerability in the global sets reordering functionality. An authenticated attacker can manipulate requests to the reorder-sets endpoint to perform actions they should not be authorized to perform. The vulnerability requires valid user credentials but does not require any special privileges or user interaction. Upgrading to version 4.18.1 eliminates the issue.
Source data · NVD / CISA · public domain
- CVSS
- 3.1 · 4.3 MEDIUM · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N
- Weaknesses (CWE)
- CWE-285, CWE-639
- Affected products
- 0 configuration(s)
- Published / Modified
- 2026-07-06 / 2026-07-06
NVD description (verbatim)
A vulnerability was detected in Craft CMS up to 4.18.0.1. Affected is the function actionReorderSets of the file src/controllers/GlobalsController.php of the component reorder-sets Endpoint. The manipulation results in authorization bypass. The attack can be executed remotely. Upgrading to version 4.18.1 is able to address this issue. The patch is identified as 9bd05c91e6a7e6da5e949ec41a31c220c059aa04. The affected component should be upgraded.
6 reference(s) · View on NVD →
SEC.co analysis · AI-assisted, reviewed against source
Technical summary
The vulnerability exists in the actionReorderSets method within src/controllers/GlobalsController.php. The endpoint fails to properly validate user permissions before allowing reordering operations on global sets. This authorization flaw (CWE-285, CWE-639) allows authenticated users to bypass access controls and modify global sets they would otherwise be restricted from changing. The vulnerability is network-accessible and requires only valid authentication credentials to exploit.
Business impact
Organizations running Craft CMS may face data integrity risks if unauthorized users modify critical global site settings. Global sets often control content, configuration, and site-wide variables; unauthorized changes could deface content, alter user-facing site behavior, or disrupt site functionality. The impact is typically limited to integrity (not confidentiality or availability), making this a moderate business concern requiring timely remediation but not an emergency.
Affected systems
Craft CMS versions 4.18.0.1 and earlier are vulnerable. The issue is resolved in version 4.18.1 and later. Organizations should verify their current Craft CMS version immediately. This affects any Craft CMS installation where the GlobalsController component is active, which is standard in typical deployments.
Exploitability
Exploitation requires valid authentication credentials—an attacker cannot exploit this remotely without a user account. However, the low complexity of the attack (once authenticated) and the lack of any user interaction requirement make this straightforward for insiders or those who have obtained user credentials through other means. The CVSS 3.1 score of 4.3 reflects the authentication requirement that limits attack surface to logged-in users.
Remediation
Upgrade Craft CMS to version 4.18.1 or later immediately. The patch commit 9bd05c91e6a7e6da5e949ec41a31c220c059aa04 implements proper authorization checks in the actionReorderSets method. After upgrading, verify that global set permissions are properly enforced by testing with restricted user accounts.
Patch guidance
Apply the official Craft CMS update to version 4.18.1 via your normal package management process. Verify the patch commit hash 9bd05c91e6a7e6da5e949ec41a31c220c059aa04 in your upgrade to confirm authenticity. Test the upgrade in a staging environment first to ensure no custom code or plugins are incompatible. Plan the upgrade during a maintenance window if your site receives continuous traffic.
Detection guidance
Monitor application logs for unusual requests to the /globals/reorder-sets endpoint or actionReorderSets method, particularly from user accounts with lower privilege levels. Look for modifications to global sets by users who do not normally have permission to edit them. Check your Craft CMS version number regularly (Configuration → System Info) and set alerts for version drift. Review user activity logs for unauthorized changes to global settings.
Why prioritize this
While the CVSS score is moderate (4.3), the vulnerability should be prioritized because it directly impacts data integrity through authorization bypass, affects authenticated users who may have legitimate access to other site areas, and patches are readily available. Organizations should plan remediation within 2-4 weeks depending on deployment complexity and risk tolerance.
Risk score, explained
The CVSS 3.1 score of 4.3 (MEDIUM severity) reflects: network accessibility (AV:N) allowing remote exploitation; low attack complexity (AC:L) making exploitation straightforward once authenticated; requirement for valid login credentials (PR:L) that limits attack surface; no impact on confidentiality (C:N); limited integrity impact (I:L) affecting only specific settings; and no availability impact (A:N). The score appropriately flags this as a business-logic authorization issue rather than a critical vulnerability, but one requiring timely attention.
Frequently asked questions
Can this vulnerability be exploited without a Craft CMS user account?
No. The vulnerability requires valid authentication credentials. An attacker must have a legitimate user account to attempt exploitation. This significantly limits the attack surface compared to unauthenticated vulnerabilities.
Does upgrading to 4.18.1 require downtime or data migration?
Upgrading between minor versions in Craft CMS is typically straightforward and does not require data migration. Follow your normal update procedures; test in staging first. Downtime depends on your deployment strategy, but is generally minimal.
How do I verify that my instance is vulnerable?
Check your Craft CMS version in Settings → System Info. If you are running version 4.18.0.1 or earlier, you are vulnerable. If you are on 4.18.1 or later, the vulnerability is patched. If you cannot upgrade immediately, restrict global set editing permissions to trusted administrators.
What should I do if I cannot upgrade immediately?
Reduce the risk by limiting who has permission to access the globals controller. Review user roles and permissions to ensure only fully trusted administrators can edit global sets. Monitor logs closely for suspicious activity on the reorder-sets endpoint and audit recent changes to global settings for unauthorized modifications.
This analysis is based on publicly disclosed vulnerability information current as of the publication date. Security teams should verify all patch version numbers and deployment guidance against official Craft CMS advisories before implementation. CVSS scores and severity ratings reflect the base vulnerability only and may not account for specific organizational context, compensating controls, or custom Craft CMS configurations. This explainer does not constitute professional security advice; consult with your security team or a qualified vendor representative for guidance specific to your environment. Source: NVD (public-domain), retrieved 2026-08-14. Analysis generated by SEC.co (claude-haiku-4-5).
Related vulnerabilities
- CVE-2026-10154MEDIUMDolibarr ERP CRM Authorization Bypass in Messaging Module
- CVE-2026-10212MEDIUMAstrBot 4.24.2 Authorization Bypass via Session ID Manipulation
- CVE-2026-11461MEDIUMhermes-agent Authorization Bypass in Resume Endpoint
- CVE-2026-11500MEDIUMWeaviate Authorization Bypass in Static API Key Handler
- CVE-2026-13512MEDIUMDatabend Authorization Bypass in Session Manager
- CVE-2026-13534MEDIUMAuthorization Bypass in CherryHQ cherry-studio Memory Service
- CVE-2026-13549MEDIUMAuthorization Bypass in CodeAstro Complaint Management System 1.0
- CVE-2026-14608MEDIUMSourceCodester CET Grading System Authorization Bypass