What is the CVSS score of CVE-2026-30944?

CVE-2026-30944 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.0%.

Which versions of Studiocms are affected by CVE-2026-30944?

StudioCMS installations are vulnerable to privilege escalation where authenticated editors can generate API tokens for admin and owner accounts, potentially gaining unauthorized administrative…. A patch is available.

How to fix or mitigate CVE-2026-30944?

Within 24 hours: Audit API token creation logs and revoke any suspicious tokens; restrict editor role permissions if possible. Within 7 days: Upgrade StudioCMS to version 0.4.0 or later when available; if unavailable, implement network-level access controls to the /studiocms_api/dashboard/api-tokens endpoint. Within 30 days: Conduct a security review of all API tokens in use and implement role-based access control (RBAC) validation on the backend.

Studiocms CVE-2026-30944

HIGH

Authorization Bypass Through User-Controlled Key (CWE-639)

2026-03-10 security-advisories@github.com

GHSA-667w-mmh7-mrr4

Privilege Escalation Authentication Bypass Studiocms

8.8

CVSS 3.1 · GitHub Advisory

Severity by source

GitHub Advisory PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from GitHub Advisory · only source for this CVE.

CVSS VectorGitHub Advisory

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Patch released

Mar 31, 2026 - 21:13 nvd

Patch available

Analysis Generated

Mar 12, 2026 - 21:55 vuln.today

CVE Published

Mar 10, 2026 - 18:18 nvd

HIGH 8.8

DescriptionGitHub Advisory

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.

AnalysisAI

Privilege escalation in StudioCMS versions prior to 0.4.0 enables authenticated Editor-level users to generate API tokens for arbitrary accounts, including administrative and owner roles, due to missing authorization validation on the /studiocms_api/dashboard/api-tokens endpoint. An attacker with basic editor privileges can exploit this to gain full administrative access without requiring the target account's credentials. No patch is currently available for affected installations.

Technical ContextAI

This vulnerability (CWE-639: Authorization Bypass Through User-Controlled Key) exists in the accounts. The component. 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.