StudioCMS Affected by Privilege Escalation via Insecure API Token Generation
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| withstudiocms | studiocms | affected |
|
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Withstudiocms | Studiocms |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-667w-mmh7-mrr4 | StudioCMS has Privilege Escalation via Insecure API Token Generation |
No CVSS v4.0
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.641% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Studiocms
Studiocms studiocms |
|
| CPEs | cpe:2.3:a:studiocms:studiocms:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Studiocms
Studiocms studiocms |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Withstudiocms
Withstudiocms studiocms |
|
| Vendors & Products |
Withstudiocms
Withstudiocms studiocms |
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | StudioCMS Affected by Privilege Escalation via Insecure API Token Generation | |
| Weaknesses | CWE-639 CWE-863 |
|
| References |
| |
| Metrics |
cvssV3_1
|