StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.0, the /studiocms_api/dashboard/api-tokens endpoint allows any authenticated user (at least Editor) to generate API tokens for any other user, including owner and admin accounts. The endpoint fails to validate whether the requesting user is authorized to create tokens on behalf of the target user ID, resulting in a full privilege escalation.
This vulnerability is fixed in 0.4.0.
Attack Parameters
Attack Vector
Network
Can be exploited remotely
Attack Complexity
Low
Easy to exploit
Privileges Required
Low
Basic privileges needed
User Interaction
None
No user interaction needed
Impact Assessment
Confidentiality
High
Complete data leak
Integrity
High
Complete data modification
Availability
High
Complete denial of service
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.0
|
References 3
https://github.com/withstudiocms/studiocms/commit/f4a209fc090c90195e2419fff47b4…
security-advisories@github.com
https://github.com/withstudiocms/studiocms/releases/tag/studiocms@0.4.0
security-advisories@github.com
https://github.com/withstudiocms/studiocms/security/advisories/GHSA-667w-mmh7-m…
security-advisories@github.com