StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.3.1, the S3 storage manager's isAuthorized() function is declared async (returns Promise<boolean>) but is called without await in both the POST and PUT handlers. Since a Promise object is always truthy in JavaScript, !isAuthorized(type) always evaluates to false, completely bypassing the authorization check. Any authenticated user with the lowest visitor role can upload, delete, rename, and list all files in the S3 bucket. This vulnerability is fixed in 0.3.1.
References
| Link | Resource |
|---|---|
| https://github.com/withstudiocms/studiocms/security/advisories/GHSA-mm78-fgq8-6pgr | Exploit Vendor Advisory |
Configurations
History
17 Mar 2026, 15:24
| Type | Values Removed | Values Added |
|---|---|---|
| CPE | cpe:2.3:a:studiocms:studiocms:*:*:*:*:*:*:*:* | |
| Summary |
|
|
| First Time |
Studiocms studiocms
Studiocms |
|
| References | () https://github.com/withstudiocms/studiocms/security/advisories/GHSA-mm78-fgq8-6pgr - Exploit, Vendor Advisory |
11 Mar 2026, 21:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-03-11 21:16
Updated : 2026-03-17 15:24
NVD link : CVE-2026-32101
Mitre link : CVE-2026-32101
CVE.ORG link : CVE-2026-32101
JSON object : View
Products Affected
studiocms
- studiocms
CWE
CWE-863
Incorrect Authorization
