| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-mm78-fgq8-6pgr | StudioCMS S3 Storage Manager Authorization Bypass via Missing `await` on Async Auth Check |
Solution
No solution given by the vendor.
Workaround
No workaround given by the vendor.
Tue, 17 Mar 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Studiocms studiocms
|
|
| CPEs | cpe:2.3:a:studiocms:studiocms:*:*:*:*:*:*:*:* | |
| Vendors & Products |
Studiocms studiocms
|
Thu, 12 Mar 2026 20:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 12 Mar 2026 10:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Studiocms
Studiocms s3-storage |
|
| Vendors & Products |
Studiocms
Studiocms s3-storage |
Wed, 11 Mar 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Title | StudioCMS S3 Storage Manager Authorization Bypass via Missing `await` on Async Auth Check | |
| Weaknesses | CWE-863 | |
| References |
| |
| Metrics |
cvssV3_1
|
Projects
Sign in to view the affected projects.
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-03-12T19:51:19.210Z
Reserved: 2026-03-10T22:02:38.854Z
Link: CVE-2026-32101
Updated: 2026-03-12T19:51:16.394Z
Status : Analyzed
Published: 2026-03-11T21:16:16.010
Modified: 2026-03-17T15:24:39.413
Link: CVE-2026-32101
No data.
OpenCVE Enrichment
Updated: 2026-03-12T09:56:17Z
Github GHSA