CVE-2026-32104

The record

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.

Affected packages

Related vulnerabilities

• GHSA-9v82-xrm4-mp52 StudioCMS: IDOR in User Notification Preferences Allows Any Authenticated User to Modify… Same vulnerability
• CVE-2026-32638 StudioCMS is a server-side-rendered, Astro native, headless content management system. Also affects studiocms
• GHSA-xvf4-ch4q-2m24 StudioCMS REST getUsers Exposes Owner Account Records to Admin Tokens Also affects studiocms
• GHSA-wj56-g96r-673q StudioCMS: REST API Missing Rank Check Allows Admin to Create Peer Admin Accounts Also affects studiocms
• GHSA-h7vr-cg25-jf8c StudioCMS: IDOR — Admin-to-Owner Account Takeover via Password Reset Link Generation Also affects studiocms
• CVE-2026-32106 StudioCMS is a server-side-rendered, Astro native, headless content management system. Also affects studiocms
• CVE-2026-32103 StudioCMS is a server-side-rendered, Astro native, headless content management system. Also affects studiocms
• GHSA-8rgj-vrfr-6hqr StudioCMS: IDOR — Arbitrary API Token Revocation Leading to Denial of Service Also affects studiocms