Vulnerability Description
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.
CVSS Score
MEDIUM
Affected Products
| Vendor | Product | Versions |
|---|---|---|
| Studiocms | Studiocms | < 0.4.3 |
Related Weaknesses (CWE)
References
- https://github.com/withstudiocms/studiocms/security/advisories/GHSA-9v82-xrm4-mpExploitVendor Advisory
FAQ
What is CVE-2026-32104?
CVE-2026-32104 is a vulnerability with a CVSS score of 5.4 (MEDIUM). 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 up...
How severe is CVE-2026-32104?
CVE-2026-32104 has been rated MEDIUM with a CVSS base score of 5.4/10. Review the CVSS metrics above for detailed severity breakdown.
Is there a patch for CVE-2026-32104?
Check the references section above for vendor advisories and patch information. Affected products include: Studiocms Studiocms.