Is this vulnerability remotely exploitable?

Yes. Any remote attacker who can obtain a valid StudioCMS account with at least Editor privileges and reach the dashboard API endpoint could exploit this issue, without needing direct server access.

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

The attacker must be an authenticated user with the minimum role that can access the `/studiocms_api/dashboard/api-tokens` endpoint (described as Editor or above). From there, they can generate tokens for higher-privileged accounts.

What is the safest general fix pattern for developers?

Implement strict authorization checks on the token generation endpoint so that: - Non-admin users can only create tokens for themselves, ignoring any client-supplied user ID. - Administrative roles explicitly validate that they are allowed to manage tokens for other users. Centralizing authorization logic and enforcing consistent patterns across all sensitive endpoints is key.

Severity:

HIGH RISK

(8.8)

Improper Authorization on API Token Generation (CWE-639) in StudioCMS Dashboard Endpoint

CVE-2026-30944

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:

Improper Authorization / Insecure Direct Object Reference

CWE:

CWE-639;CWE-863

Impact:

Privilege Escalation via Unauthorized Token Creation

Severity:

HIGH RISK

(8.8)

CVSS Version:

3.1

Vulnerability Type

Category:

Improper Authorization / Insecure Direct Object Reference

CWE:

CWE-639;CWE-863

Impact:

Privilege Escalation via Unauthorized Token Creation

Severity:

HIGH RISK

(8.8)

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

Improper Authorization on API Token Generation (CWE-639) in StudioCMS Dashboard 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