StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.3, the updateUserNotifications endpoint accepts a user ID from the request payload and uses it to update that user's notification preferences. It checks that the caller is logged in but never verifies that the caller owns the target account (id !== userData.user.id). Any authenticated visitor can modify notification preferences for any user, including disabling admin notifications to suppress detection of malicious activity. This vulnerability is fixed in 0.4.3.
References
| Link | Resource |
|---|---|
| https://github.com/withstudiocms/studiocms/security/advisories/GHSA-9v82-xrm4-mp52 | Exploit Vendor Advisory |
Configurations
History
17 Mar 2026, 15:35
| Type | Values Removed | Values Added |
|---|---|---|
| References | () https://github.com/withstudiocms/studiocms/security/advisories/GHSA-9v82-xrm4-mp52 - Exploit, Vendor Advisory | |
| First Time |
Studiocms studiocms
Studiocms |
|
| Summary |
|
|
| CPE | cpe:2.3:a:studiocms:studiocms:*:*:*:*:*:*:*:* |
11 Mar 2026, 21:16
| Type | Values Removed | Values Added |
|---|---|---|
| New CVE |
Information
Published : 2026-03-11 21:16
Updated : 2026-03-17 15:35
NVD link : CVE-2026-32104
Mitre link : CVE-2026-32104
CVE.ORG link : CVE-2026-32104
JSON object : View
Products Affected
studiocms
- studiocms
CWE
CWE-639
Authorization Bypass Through User-Controlled Key
