7.1
HIGH CVSS 3.1
CVE-2026-30945
StudioCMS: IDOR — Arbitrary API Token Revocation Leading to Denial of Service
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.

INFO

Published Date :

March 10, 2026, 6:18 p.m.

Last Modified :

March 17, 2026, 4:17 p.m.

Remotely Exploit :

Yes !
Affected Products

The following products are affected by CVE-2026-30945 vulnerability. Even if cvefeed.io is aware of the exact versions of the products that are affected, the information is not represented in the table below.

ID Vendor Product Action
1 Studiocms studiocms
CVSS Scores
The Common Vulnerability Scoring System is a standardized framework for assessing the severity of vulnerabilities in software and systems. We collect and displays CVSS scores from various sources for each CVE.
Score Version Severity Vector Exploitability Score Impact Score Source
CVSS 3.1 HIGH [email protected]
CVSS 3.1 HIGH MITRE-CVE
Solution
Update StudioCMS to version 0.4.0 or later to fix authorization issues.
  • Update StudioCMS to version 0.4.0.
  • Verify API token ownership and permissions.
Public PoC/Exploit Available at Github

CVE-2026-30945 has a 2 public PoC/Exploit available at Github. Go to the Public Exploits tab to see the list.

References to Advisories, Solutions, and Tools

Here, you will find a curated list of external links that provide in-depth information, practical solutions, and valuable tools related to CVE-2026-30945.

URL Resource
https://github.com/withstudiocms/studiocms/commit/9eec9c3b45523b635cfe16d55aa55afabacbebe3 Patch
https://github.com/withstudiocms/studiocms/releases/tag/[email protected] Product
https://github.com/withstudiocms/studiocms/security/advisories/GHSA-8rgj-vrfr-6hqr Exploit Vendor Advisory
CWE - Common Weakness Enumeration

While CVE identifies specific instances of vulnerabilities, CWE categorizes the common flaws or weaknesses that can lead to vulnerabilities. CVE-2026-30945 is associated with the following CWEs:

Common Attack Pattern Enumeration and Classification (CAPEC)

Common Attack Pattern Enumeration and Classification (CAPEC) stores attack patterns, which are descriptions of the common attributes and approaches employed by adversaries to exploit the CVE-2026-30945 weaknesses.

We scan GitHub repositories to detect new proof-of-concept exploits. Following list is a collection of public exploits and proof-of-concepts, which have been published on GitHub (sorted by the most recently updated).

None

Python

Updated: 3 weeks, 3 days ago
0 stars 0 fork 0 watcher
Born at : March 11, 2026, 10:33 p.m. This repo has been linked 2 different CVEs too.

📡 PoC auto collect from GitHub. ⚠️ Be careful Malware.

security cve exploit poc vulnerability

Updated: 2 hours, 22 minutes ago
7620 stars 1243 fork 1243 watcher
Born at : Dec. 8, 2019, 1:03 p.m. This repo has been linked 766 different CVEs too.

Results are limited to the first 15 repositories due to potential performance issues.

The following list is the news that have been mention CVE-2026-30945 vulnerability anywhere in the article.

The following table lists the changes that have been made to the CVE-2026-30945 vulnerability over time.

Vulnerability history details can be useful for understanding the evolution of a vulnerability, and for identifying the most recent changes that may impact the vulnerability's severity, exploitability, or other characteristics.

  • Initial Analysis by [email protected]

    Mar. 17, 2026

    Action Type Old Value New Value
    Added CPE Configuration OR *cpe:2.3:a:studiocms:studiocms:*:*:*:*:*:*:*:* versions up to (excluding) 0.4.0
    Added Reference Type GitHub, Inc.: https://github.com/withstudiocms/studiocms/commit/9eec9c3b45523b635cfe16d55aa55afabacbebe3 Types: Patch
    Added Reference Type GitHub, Inc.: https://github.com/withstudiocms/studiocms/releases/tag/[email protected] Types: Product
    Added Reference Type GitHub, Inc.: https://github.com/withstudiocms/studiocms/security/advisories/GHSA-8rgj-vrfr-6hqr Types: Exploit, Vendor Advisory
  • New CVE Received by [email protected]

    Mar. 10, 2026

    Action Type Old Value New Value
    Added 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.
    Added CVSS V3.1 AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:H
    Added CWE CWE-639
    Added CWE CWE-863
    Added Reference https://github.com/withstudiocms/studiocms/commit/9eec9c3b45523b635cfe16d55aa55afabacbebe3
    Added Reference https://github.com/withstudiocms/studiocms/releases/tag/[email protected]
    Added Reference https://github.com/withstudiocms/studiocms/security/advisories/GHSA-8rgj-vrfr-6hqr
EPSS is a daily estimate of the probability of exploitation activity being observed over the next 30 days. Following chart shows the EPSS score history of the vulnerability.