CVE-2026-30945: withstudiocms studiocms · Insecure Direct Object Reference
Affects withstudiocms studiocmsSource CVE Database V5
Not known to be exploited · CVSS 7.1 High : upgrade to 0.4.0 soon.
Data as of 30 Oct 2026, 11:52 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 41% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 0.4.0
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:HExploitation evidence
Disclosed: evidence found.
CVE published 10 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
Public exploit code: GitHub proofs of concept
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.
What to do
Upgrade studiocms and withstudiocms/studiocms to 0.4.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| withstudiocmsstudiocms | Affected
| Fixed in
|
GitHubwithstudiocms/studiocmspkg:github/withstudiocms/studiocmsOther threats | Affected
| Fixed in
|
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 StudioCMS to version 0.4.0 or later, where this vulnerability is fixed with proper authorization checks. Until upgrading, restrict editor-level privileges to trusted users only and monitor API token revocation activities closely for suspicious behavior. Implement compensating controls such as logging and alerting on API token revocation requests to detect unauthorized attempts. Review and tighten role-based access control policies to minimize the number of users with editor or higher privileges. Consider isolating critical integrations and automations to use dedicated service accounts with limited token revocation rights. Additionally, conduct regular audits of API tokens and their usage to quickly identify and remediate disruptions. Employ network segmentation and zero-trust principles to limit lateral movement if an editor-level account is compromised. Finally, educate administrators and users about the risks associated with token management and enforce strong authentication mechanisms.
Description
CVE-2026-30945 is a high-severity authorization bypass vulnerability in StudioCMS versions prior to 0.4.0. It allows any authenticated user with editor privileges or higher to revoke API tokens belonging to other users, including administrators and owners, without proper ownership or role verification. This occurs because the DELETE /studiocms_api/dashboard/api-tokens endpoint accepts tokenID and userID directly from the request payload without validating the caller's identity or role hierarchy. Exploiting this flaw can lead to denial of service against critical integrations and automations relying on those API tokens. The vulnerability does not require user interaction and can be exploited remotely over the network. It is fixed in StudioCMS version 0.4.0.