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

High 8.8 Published Updated

Authenticated editors can generate API tokens for admin accounts, enabling full privilege escalation and account takeover in StudioCMS.

Exploited in the wild
Not known
Login needed
Any signed-in user
Attackable
Over the internet
Victim action needed
Not needed
Fix
Available

What is CVE-2026-30944?

CVE-2026-30944 is a high-severity vulnerability in withstudiocms studiocms, published on 10 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

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.

Weakness: CWE-863, CWE-639

Which versions are affected by CVE-2026-30944?

2 open source packages ship an affected version, including studiocms. It affects 1 product.

PackageAffectedFixed in
studiocms npmAll versions0.4.0
studiocms npmAll versions0.4.0

Products include Studiocms Studiocms.

How do I fix CVE-2026-30944?

Upgrade studiocms to 0.4.0 or later.

Is CVE-2026-30944 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-30944 exists.

Public exploit code: 1 proofs of concept on GitHub.

Sources

Also known as GHSA-667w-mmh7-mrr4.

Is CVE-2026-30944 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free