CVE-2026-30944
High · 8.8CVSS
8.8
EPSS
0.6%
Published
Mar 10, 2026
CISA due date
—
The record
StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.0, the /studiocms_api/dashboard/api-tokens endpoint allows any authenticated user (at least Editor) to generate API tokens for any other user, including owner and admin accounts. The endpoint fails to validate whether the requesting user is authorized to create tokens on behalf of the target user ID, resulting in a full privilege escalation. This vulnerability is fixed in 0.4.0.
Affected packages
| Ecosystem | Package | Introduced | Fixed |
|---|---|---|---|
| npm | studiocms | 0 | 0.4.0 |
Related vulnerabilities
- GHSA-667w-mmh7-mrr4 StudioCMS has Privilege Escalation via Insecure API Token Generation Same vulnerability
- CVE-2026-32638 StudioCMS is a server-side-rendered, Astro native, headless content management system. Also affects studiocms
- GHSA-xvf4-ch4q-2m24 StudioCMS REST getUsers Exposes Owner Account Records to Admin Tokens Also affects studiocms
- GHSA-wj56-g96r-673q StudioCMS: REST API Missing Rank Check Allows Admin to Create Peer Admin Accounts Also affects studiocms
- GHSA-9v82-xrm4-mp52 StudioCMS: IDOR in User Notification Preferences Allows Any Authenticated User to Modify… Also affects studiocms
- GHSA-h7vr-cg25-jf8c StudioCMS: IDOR — Admin-to-Owner Account Takeover via Password Reset Link Generation Also affects studiocms
- CVE-2026-32106 StudioCMS is a server-side-rendered, Astro native, headless content management system. Also affects studiocms
- CVE-2026-32103 StudioCMS is a server-side-rendered, Astro native, headless content management system. Also affects studiocms