CVE-2026-32106: StudioCMS REST API Missing Rank Check Vulnerability
MODERATECVE-2026-32106 is a MODERATE (CVSS 4.7) rest api missing rank check vulnerability (CWE-269: Improper Privilege Management) affecting StudioCMS libraries in the npm ecosystem. The issue involves rest api missing rank check allows admin to create peer admin accounts. Remediation is available by upgrading affected packages to version 0.4.3.
CVE-2026-32106 at a Glance
Security Impact
CVSS: 4.7
The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L).
How to Fix CVE-2026-32106
To remediate this vulnerability, upgrade all affected StudioCMS dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.
npm install studiocms@0.4.3
Run the following command in your project directory to verify that all resolved dependencies use the patched release:
npm ls studiocms
How to Check if You Are Affected
To determine whether your Node.js application is affected by CVE-2026-32106, inspect your project dependencies using npm:
npm ls studiocms
Analyze the terminal output to locate any version of StudioCMS in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 0.4.3), your application is affected.
Note: The npm ls studiocms command inspects dependencies declared in your package.json and lockfile; it does not perform automated runtime dynamic scanning.
Technical Details
Vulnerability Mechanism & Technical Analysis
This vulnerability is classified under CWE-269: Improper Privilege Management, where the product does not properly assign, modify, track, or check privileges for an actor, creating an unintended sphere of control for that actor. In StudioCMS, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.
Source Advisory Statement
CVE-2026-32106 Affected StudioCMS Versions
1 component(s)| Product / Package | Ecosystem | Affected Versions | Fixed Version |
|---|---|---|---|
|
studiocms
|
npm |
< 0.4.3
|
0.4.3
|
References
Frequently Asked Questions
What is CVE-2026-32106?
Which StudioCMS versions are affected?
What version fixes CVE-2026-32106?
Is studiocms affected?
What is the CVSS score of CVE-2026-32106?
What CWE is associated with CVE-2026-32106?
How can I check npm dependencies for CVE-2026-32106?
Machine-readable OSV JSON
OSV v1.5 Schema
{
"schema_version" : "1.4.0",
"id" : "GHSA-wj56-g96r-673q",
"modified" : "2026-03-12T14:49:48Z",
"published" : "2026-03-12T14:49:48Z",
"aliases" : [ "CVE-2026-32106" ],
"summary" : "StudioCMS: REST API Missing Rank Check Allows Admin to Create Peer Admin Accounts",
"details" : "## Summary\n\nThe 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.\n\n## Details\n\nThe REST API handler in `packages/studiocms/frontend/pages/studiocms_api/_handlers/rest-api/v1/secure.ts:1365-1378`:\n\n```typescript\n// REST API — only blocks creating 'owner'\nif (newUserRank === 'owner' && rank !== 'owner') {\n return yield* new RestAPIError({\n error: 'Unauthorized to create user with owner rank',\n });\n}\n\nif (rank === 'admin' && newUserRank === 'owner') {\n return yield* new RestAPIError({\n error: 'Unauthorized to create user with owner rank',\n });\n}\n\n// Missing: no check preventing admin from creating admin\n// newUserRank='admin' passes all checks\n```\n\nThe Dashboard API handler in `_handlers/dashboard/create.ts` uses the correct approach:\n\n```typescript\n// Dashboard API — blocks creating users at or above own rank\nconst callerPerm = availablePermissionRanks.indexOf(userData.permissionLevel);\nconst targetPerm = availablePermissionRanks.indexOf(rank);\n\nif (targetPerm >= callerPerm) {\n return yield* new DashboardAPIError({\n error: 'Unauthorized: insufficient permissions to assign target rank',\n });\n}\n```\n\nWith `availablePermissionRanks = ['unknown', 'visitor', 'editor', 'admin', 'owner']`:\n- Admin (index 3) creating admin (index 3): `3 >= 3` = blocked in Dashboard\n- In REST API: no such check — allowed\n\n## PoC\n\n```bash\n# 1. Use an admin-level API token\n\n# 2. Create a new admin user via REST API\ncurl -X POST 'http://localhost:4321/studiocms_api/rest/v1/secure/users' \\\n -H 'Authorization: Bearer <admin-api-token>' \\\n -H 'Content-Type: application/json' \\\n -d '{\n \"username\": \"rogue_admin\",\n \"email\": \"rogue@attacker.com\",\n \"displayname\": \"Rogue Admin\",\n \"rank\": \"admin\",\n \"password\": \"StrongP@ssw0rd123\"\n }'\n\n# Expected: 403 Forbidden (admin should not create peer admin accounts)\n# Actual: 200 with new admin user created\n```\n\n## Impact\n\n- A compromised or rogue admin can create additional admin accounts as persistence mechanisms that survive password resets or token revocations\n- Inconsistent security model between Dashboard API and REST API creates confusion about intended authorization boundaries\n- Note: requires admin access (PR:H), which limits practical severity\n\n## Recommended Fix\n\nReplace string-based checks with `indexOf` comparison in `packages/studiocms/frontend/pages/studiocms_api/_handlers/rest-api/v1/secure.ts`:\n\n```typescript\n// Before:\nif (newUserRank === 'owner' && rank !== 'owner') { ... }\nif (rank === 'admin' && newUserRank === 'owner') { ... }\n\n// After:\nconst availablePermissionRanks = ['unknown', 'visitor', 'editor', 'admin', 'owner'];\nconst callerPerm = availablePermissionRanks.indexOf(rank);\nconst targetPerm = availablePermissionRanks.indexOf(newUserRank);\n\nif (targetPerm >= callerPerm) {\n return yield* new RestAPIError({\n error: 'Unauthorized: insufficient permissions to assign target rank',\n });\n}\n```",
"severity" : [ {
"type" : "CVSS_V3",
"score" : "CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:L/A:L"
} ],
"affected" : [ {
"package" : {
"ecosystem" : "npm",
"name" : "studiocms"
},
"ranges" : [ {
"type" : "ECOSYSTEM",
"events" : [ {
"introduced" : "0"
}, {
"fixed" : "0.4.3"
} ]
} ],
"database_specific" : {
"last_known_affected_version_range" : "<= 0.4.2"
}
} ],
"references" : [ {
"type" : "WEB",
"url" : "https://github.com/withstudiocms/studiocms/security/advisories/GHSA-wj56-g96r-673q"
}, {
"type" : "ADVISORY",
"url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-32106"
}, {
"type" : "PACKAGE",
"url" : "https://github.com/withstudiocms/studiocms"
} ],
"database_specific" : {
"cwe_ids" : [ "CWE-269" ],
"severity" : "MODERATE",
"github_reviewed" : true,
"github_reviewed_at" : "2026-03-12T14:49:48Z",
"nvd_published_at" : "2026-03-11T21:16:16Z"
}
}