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.

Affected: npm: studiocms

## Summary 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.

## Details #### Vulnerable Code The following is the server-side handler for the `DELETE /studiocms_api/dashboard/api-tokens` endpoint (`revokeApiToken`):

**File:** packages/studiocms/frontend/pages/studiocms_api/dashboard/api-tokens.ts (lines 58–99) **Version:** studiocms@0.3.0 ``` DELETE: (ctx) => genLogger('studiocms/routes/api/dashboard/api-tokens.DELETE')(function* () { const sdk = yield* SDKCore;

// Check if demo mode is enabled if (developerConfig.demoMode !== false) { return apiResponseLogger(403, 'Demo mode is enabled, this action is not allowed.'); }

// Get user data const userData = ctx.locals.StudioCMS.security?.userSessionData; // [1]

// Check if user is logged in if (!userData?.isLoggedIn) { // [2] return apiResponseLogger(403, 'Unauthorized'); }

// Check if user has permission const isAuthorized = ctx.locals.StudioCMS.security?.userPermissionLevel.isEdito…