Studiocms
CVE-2026-32106
MEDIUM
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V8 - Authorization Least privilege enforcement
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Impact | An attacker with limited access can gain administrative or root privileges, enabling full control over the affected system. With a CVSS score of 4.7 (MEDIUM), this represents a moderate risk. |
| Exploit ScenarioDerived | A local attacker exploits a vulnerability in a privileged service or misconfigured permissions to escalate from a standard user to root/administrator. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Mar 12, 2026
Summary
The REST API createUser endpoint uses string-based rank checks that only block creating owner accounts, while the Dashboard API uses indexOf-based rank comparison that prevents creating users at or above your own rank. This inconsistency allows an admin to create additional admin accounts via the REST API, enabling privilege proliferation and persistence.
Details
The REST API handler in packages/studiocms/frontend/pages/studiocms_api/_handlers/rest-api/v1/secure.ts:1365-1378:
// REST API - only blocks creating 'owner'
if (newUserRank === 'owner' && rank !== 'owner') {
return yield* new RestAPIError({
error: 'Unauthorized to create user with owner rank',
});
}
if (rank === 'admin' && newUserRank === 'owner') {
return yield* new RestAPIError({
error: 'Unauthorized to create user with owner rank',
});
}
// Missing: no check preventing admin from creating admin
// newUserRank='admin' passes all checksThe Dashboard API handler in _handlers/dashboard/create.ts uses the correct approach:
// Dashboard API - blocks creating users at or above own rank
const callerPerm = availablePermissionRanks.indexOf(userData.permissionLevel);
const targetPerm = availablePermissionRanks.indexOf(rank);
if (targetPerm >= callerPerm) {
return yield* new DashboardAPIError({
error: 'Unauthorized: insufficient permissions to assign target rank',
});
}With availablePermissionRanks = ['unknown', 'visitor', 'editor', 'admin', 'owner']:
- Admin (index 3) creating admin (index 3):
3 >= 3= blocked in Dashboard - In REST API: no such check - allowed
PoC
# 1. Use an admin-level API token
# 2. Create a new admin user via REST API
curl -X POST 'http://localhost:4321/studiocms_api/rest/v1/secure/users' \
-H 'Authorization: Bearer <admin-api-token>' \
-H 'Content-Type: application/json' \
-d '{
"username": "rogue_admin",
"email": "rogue@attacker.com",
"displayname": "Rogue Admin",
"rank": "admin",
"password": "StrongP@ssw0rd123"
}'
# Expected: 403 Forbidden (admin should not create peer admin accounts)
# Actual: 200 with new admin user createdImpact
- A compromised or rogue admin can create additional admin accounts as persistence mechanisms that survive password resets or token revocations
- Inconsistent security model between Dashboard API and REST API creates confusion about intended authorization boundaries
- Note: requires admin access (PR:H), which limits practical severity
Recommended Fix
Replace string-based checks with indexOf comparison in packages/studiocms/frontend/pages/studiocms_api/_handlers/rest-api/v1/secure.ts:
// Before:
if (newUserRank === 'owner' && rank !== 'owner') { ... }
if (rank === 'admin' && newUserRank === 'owner') { ... }
// After:
const availablePermissionRanks = ['unknown', 'visitor', 'editor', 'admin', 'owner'];
const callerPerm = availablePermissionRanks.indexOf(rank);
const targetPerm = availablePermissionRanks.indexOf(newUserRank);
if (targetPerm >= callerPerm) {
return yield* new RestAPIError({
error: 'Unauthorized: insufficient permissions to assign target rank',
});
}Earlier versions of this analysis (1)
RemediationAI
Apply the principle of least privilege. Keep systems patched. Monitor for suspicious privilege changes. Use mandatory access controls (SELinux, AppArmor).
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in npm
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Privilege escalation allows a low-privileged user or process to gain elevated permissions beyond what was originally authorized. This vulnerability is classified as Improper Privilege Management (CWE-269).
Know when Studiocms gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L
Primary rating from GitHub Advisory · only source for this CVE.
CVSS VectorGitHub Advisory
Lifecycle Timeline
2DescriptionGitHub Advisory
StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.3, the REST API createUser endpoint uses string-based rank checks that only block creating owner accounts, while the Dashboard API uses indexOf-based rank comparison that prevents creating users at or above your own rank. This inconsistency allows an admin to create additional admin accounts via the REST API, enabling privilege proliferation and persistence. This vulnerability is fixed in 0.4.3.
Executive ViewAI
Organizations using StudioCMS should be aware of moderate risk from CVE-2026-32106, a improper privilege management vulnerability rated CVSS 4.7. Attackers could gain access beyond their authorized level. Organizations should apply vendor updates when available and monitor for exploitation.
Apply vendor patch. If patching is delayed: restrict network access and enable monitoring.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Affected Products (CPE)GitHub Advisory
Related Vulnerabilities in StudioCMS Authorization and Access Control
View all 5Privilege escalation in StudioCMS versions prior to 0.4.0 enables authenticated Editor-level users to generate API token
StudioCMS prior to version 0.4.0 allows authenticated editors and above to revoke API tokens belonging to any user, incl
headless content management system. versions up to 0.2.0 is affected by authorization bypass through user-controlled key
GHSA-wj56-g96r-673q
NVD
CVE.org
EPSS
VulDB
Exploit-DB