CVE-2026-63301: Quick.CMS primary language deletion authorization bypass DoS
CVE-2026-63301 is a client-side-only enforcement flaw in OpenSolution Quick.CMS affecting versions through 6.8.0. The administrative interface prevents deletion of the primary language only by hiding that option in the UI, but the backend language-deletion API does not enforce an equivalent server-side restriction. An authenticated administrator can therefore bypass the interface limitation by issuing a direct HTTP request to the language-deletion endpoint and delete the primary language. Deletion of the primary language renders the application unavailable, resulting in denial of service. The issue is classified as CWE-602 because a security restriction is implemented in the client-facing interface rather than enforced on the server.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows deletion of the application's primary language configuration, which causes denial of service and can render Quick.CMS unusable. Although direct exploitation requires an authenticated administrator session, the flaw can be chained with CVE-2026-1468, a separate CSRF vulnerability, so that an unauthenticated remote attacker can induce the destructive request if an authenticated administrator visits a malicious link.
Mitigation
If you can’t patch tonight, do this now.
No vendor mitigation was provided, and the vendor stated that a fix was not necessary. As compensating controls, administrators should avoid following untrusted links while authenticated to Quick.CMS, especially until the related CSRF issue is addressed. Restricting access to the administrative interface, minimizing active administrator sessions, and monitoring for unauthorized language-management actions can reduce exposure, but these measures do not eliminate the underlying server-side authorization flaw.
Remediation
Patch, then assume compromise.
The appropriate remediation is to enforce the primary-language deletion restriction on the server side in the language-deletion API, rather than relying on omission of the option in the administrative interface. The backend should explicitly reject attempts to delete the primary language regardless of how the request is submitted. If business logic permits language deletion under some conditions, the server should validate those conditions authoritatively. Because the issue can be chained with CVE-2026-1468, remediation should also include fixing the related CSRF weakness.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Frequently asked questions
- Is CVE-2026-63301 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2026-63301 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-63301?
- As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-63301.
- Is there a patch for CVE-2026-63301?
- The appropriate remediation is to enforce the primary-language deletion restriction on the server side in the language-deletion API, rather than relying on omission of the option in the administrative interface. The backend should explicitly reject attempts to delete the primary language regardless of how the request is submitted.
- How severe is CVE-2026-63301?
- CVE-2026-63301 has a CVSS v4 score of 7.0 (High) and an EPSS score of 0.57% (48th percentile) as of Sep 25, 2026.
Recent activity
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.