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.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
High
Admin privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
Low
Partial data leak
Integrity
None
No data modification
Availability
None
No disruption
CVSS Vector v3.1
Weakness Type (CWE)
Vulnerable Products 1
| Configuration | From (including) | Up to (excluding) |
|---|---|---|
|
Studiocms Studiocms
cpe:2.3:a:studiocms:studiocms:*:*:*:*:*:*:*:*
|
— |
0.4.4
|
References 3
https://github.com/withstudiocms/studiocms/commit/aebe8bcb3618bb07c6753e3f5c982…
security-advisories@github.com
https://github.com/withstudiocms/studiocms/releases/tag/studiocms@0.4.4
security-advisories@github.com
https://github.com/withstudiocms/studiocms/security/advisories/GHSA-xvf4-ch4q-2…
security-advisories@github.com