Vulnerability · Published Mar 10, 2026 · Assigned by GitHub_M

CVE-2026-30944StudioCMS Affected by Privilege Escalation via Insecure API Token Generation

High 8.8

In plain English

A high-severity authorization bypass via user-controlled key in studiocms from withstudiocms. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.6% (higher than 51% of all known vulnerabilities). Ready-made attack tooling exists: public proof-of-concept code. Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)8.8High
Exploit odds (30 days)0.6%top 49.1% of all CVEs
Exploited in the wildNo reportsCISA SSVC: poc
Attack tooling1Public PoC

Official description

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 & fixed versions

EcosystemPackageFixed inAdvisory
npmstudiocms0.4.0GHSA-667w-mmh7-mrr4

Affected products (as reported)

VendorProductVersions
withstudiocms studiocms < 0.4.0

Weakness: CWE-639, CWE-863 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

References