CVE-2026-32638
March 18, 2026
StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.4, the REST API "getUsers" endpoint in StudioCMS uses the attacker-controlled "rank" query parameter to decide whether owner accounts should be filtered from the result set. As a result, an admin token can request "rank=owner" and receive owner account records, including IDs, usernames, display names, and email addresses, even though the adjacent "getUser" endpoint correctly blocks admins from viewing owner users. This is an authorization inconsistency inside the same user-management surface. Version 0.4.4 fixes the issue.
Affected Packages
https://github.com/withstudiocms/studiocms.git (GITHUB):
Affected version(s) >=studiocms@0.1.0-beta.5 <studiocms@0.4.4Fix Suggestion:
Update to version studiocms@0.4.4studiocms (NPM):
Affected version(s) >=0.1.0-beta.5 <0.4.4Fix Suggestion:
Update to version 0.4.4Related Resources (5)
Do you need more information?
Contact UsCVSS v4
Base Score:
5.1
Attack Vector
NETWORK
Attack Complexity
LOW
Attack Requirements
NONE
Privileges Required
HIGH
User Interaction
NONE
Vulnerable System Confidentiality
LOW
Vulnerable System Integrity
NONE
Vulnerable System Availability
NONE
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
2.7
Attack Vector
NETWORK
Attack Complexity
LOW
Privileges Required
HIGH
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
NONE
Weakness Type (CWE)
Authorization Bypass Through User-Controlled Key
EPSS
Base Score:
0.01