Auth bypass in Studiocms
CVE-2026-32104
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.
Vulnerability class: IDOR (Insecure Direct Object Reference)
EPSS: 0.003 (16.8th percentile) — read the EPSS interpretation.
CVSS v3 metric
CVSS v3 base score 5.4 (Medium). Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L.
Affected products
- Studiocms
- Withstudiocms Studiocms — versions < 0.4.3
Weakness classification (CWE)
References
- security-advisories@github.com (x_refsource_CONFIRM, Exploit, Vendor Advisory)
Frequently asked questions
- What is CVE-2026-32104?
- CVE-2026-32104 is a medium-severity vulnerability in Studiocms, classified under Authorization Bypass Through User-Controlled Key. CVSS score: 5.4/10. Published 2026-03-11.
- How severe is CVE-2026-32104?
- Medium severity. CVSS v3 base score is 5.4 out of 10.