S3 Storage
Approved changes feed: RSS · Atom
cpe:2.3:a:@studiocms:s3-storage:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | @Studiocms (e020c8b5-3a09-568e-a726-f1388c46b445) |
|---|---|
| Product | S3 Storage (f50abc3d-c373-52fe-8ae3-b877206b0dcb) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-32101 |
vulnerable | 2026-06-03 15:20:41.929117 |
StudioCMS S3 Storage Manager Authorization Bypass via Missing `await` on Async Auth Check
HIGH (7.6)
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.
Published: 2026-03-11T20:03:05.319Z
Updated: 2026-03-12T19:51:19.210Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.