Home

Description

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.

PUBLISHED Reserved 2026-03-07 | Published 2026-03-10 | Updated 2026-03-10 | Assigner GitHub_M




HIGH: 7.1CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H

Problem types

CWE-639: Authorization Bypass Through User-Controlled Key

CWE-863: Incorrect Authorization

Product status

< 0.4.0
affected

References

github.com/...diocms/security/advisories/GHSA-8rgj-vrfr-6hqr

github.com/...ommit/9eec9c3b45523b635cfe16d55aa55afabacbebe3

github.com/...udiocms/studiocms/releases/tag/studiocms@0.4.0

cve.org (CVE-2026-30945)

nvd.nist.gov (CVE-2026-30945)

Download JSON