StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.0, the DELETE /studiocms_api/dashboard/api-tokens endpoint allows any authenticated user with editor privileges or above to revoke API tokens belonging to any other user, including admin and owner accounts. The handler accepts tokenID and userID directly from the request payload without verifying token ownership, caller identity, or role hierarchy.
This enables targeted denial of service against critical integrations and automations. This vulnerability is fixed in 0.4.0.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
None
No data leak
Integrity
Low
Partial data modification
Availability
High
Complete denial of service
CVSS Vector v3.1
Weakness Type (CWE)
Vulnerable Products 1
| Configuration | From (including) | Up to (excluding) |
|---|---|---|
|
Studiocms Studiocms
cpe:2.3:a:studiocms:studiocms:*:*:*:*:*:*:*:*
|
— |
0.4.0
|
References 3
https://github.com/withstudiocms/studiocms/commit/9eec9c3b45523b635cfe16d55aa55…
security-advisories@github.com
https://github.com/withstudiocms/studiocms/releases/tag/studiocms@0.4.0
security-advisories@github.com
https://github.com/withstudiocms/studiocms/security/advisories/GHSA-8rgj-vrfr-6…
security-advisories@github.com