Is this vulnerability remotely exploitable?

Yes. Any user who can authenticate to the StudioCMS instance with at least editor privileges and can reach the dashboard API can exploit this over the network by issuing crafted DELETE requests.

What level of access does an attacker need to exploit this issue?

The attacker needs valid credentials for an account with editor privileges or higher. No administrative privileges are required, and the attacker does not need direct access to the victim's account—only knowledge or discovery of target token identifiers.

What is the safest general fix pattern for this type of bug?

The most robust fix is to enforce strict object-level authorization: derive the acting user from the authenticated session, verify that they own or are explicitly permitted to manage the targeted token, and restrict cross-user operations to narrowly scoped administrative paths with clear policy checks.

Severity:

HIGH RISK

(7.1)

Insecure Direct Object Reference (CWE-639) in StudioCMS API Token Deletion Endpoint

CVE-2026-30945

Published:

Mar 10, 2026

Status:

Analyzed

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

NDV

Recent Vulnerabilities

CWE-918

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

Unauthorized Access to Internal Resources via SSRF

May 6, 2026

CWE-863

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Privilege Escalation via Bypassed Access Control

May 6, 2026

Vulnerability Type

Category:

Broken Access Control / Insecure Direct Object Reference

CWE:

CWE-639;CWE-863

Impact:

Privilege Abuse and Targeted Denial of Service

Severity:

HIGH RISK

(7.1)

CVSS Version:

3.1

Vulnerability Type

Category:

Broken Access Control / Insecure Direct Object Reference

CWE:

CWE-639;CWE-863

Impact:

Privilege Abuse and Targeted Denial of Service

Severity:

HIGH RISK

(7.1)

CVSS Version:

3.1

Catch This CVE While Code Is Being Written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Get Started

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

Ship clean & secure code faster

Start Free Trial

Get Pentest Report

CodeAnt AI is an offensive and defensive security platform.

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

SOC 2 Type II certified | CodeAnt AI is independently audited and compliant with SOC 2 Type II security standards

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Defensive + offensive security.

From first line of code to a pentest
that knows every line of it.

Ask AI for summary of CodeAnt

Insecure Direct Object Reference (CWE-639) in StudioCMS API Token Deletion Endpoint

Summary

Affected Context

Exploit Preconditions

Why This Happens

Potential Impact

General Mitigation Guidance

How Teams Detect Issues Like This

Frequently Asked Questions

Source

Recent Vulnerabilities

HIGH RISK

HIGH

(8.6)

Server-Side Request Forgery (CWE-918) in OpenClaw Zalo Plugin sendPhoto

HIGH RISK

HIGH

(8.8)

Authorization Bypass (CWE-863) in OpenClaw Matrix Room Control Commands

Vulnerability Type

Vulnerability Type

Vulnerability Type

Catch This CVE While Code Is Being Written

Ship clean & secure code faster

Ship clean & secure code faster

Ship clean & secure code faster

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal

Product

Compare

Company

Developers

Legal