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

> Authenticated users can modify any other user's notification settings, potentially disabling admin alerts to hide malicious activity.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 11 Mar 2026
- **Updated:** 12 Mar 2026
- **Also known as:** GHSA-9v82-xrm4-mp52

## What is CVE-2026-32104?

CVE-2026-32104 is a medium-severity missing authorization vulnerability in withstudiocms studiocms, published on 11 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.

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

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-32104?

2 open source packages ship an affected version, including studiocms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `studiocms` | npm | All versions | 0.4.3 |
| `studiocms` | npm | All versions | 0.4.3 |

Products: Studiocms Studiocms.

## How do I fix CVE-2026-32104?

Upgrade studiocms to 0.4.3 or later.

## Is CVE-2026-32104 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32104 exists.

## Other vulnerabilities in withstudiocms studiocms

- [CVE-2026-30944](https://insights.sbomify.com/CVE-2026-30944/): StudioCMS Affected by Privilege Escalation via Insecure API Token Generation (high 8.8)
- [CVE-2026-32101](https://insights.sbomify.com/CVE-2026-32101/): StudioCMS S3 Storage Manager Authorization Bypass via Missing `await` on Async Auth Check (high 7.6)
- [CVE-2026-30945](https://insights.sbomify.com/CVE-2026-30945/): StudioCMS: IDOR — Arbitrary API Token Revocation Leading to Denial of Service (high 7.1)
- [CVE-2026-32103](https://insights.sbomify.com/CVE-2026-32103/): StudioCMS: IDOR — Admin-to-Owner Account Takeover via Password Reset Link Generation (medium 6.8)
- [CVE-2026-24134](https://insights.sbomify.com/CVE-2026-24134/): StudioCMS has an Authorization Bypass Through User-Controlled Key (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32104 and fix it if it is affected.

What it is: CVE-2026-32104 is a medium-severity missing authorization vulnerability in withstudiocms studiocms, published on 11 Mar 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32104 exists.

Affected packages and fixed versions:
- studiocms (npm): affected all versions; fixed in 0.4.3
- studiocms (npm): affected all versions; fixed in 0.4.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32104/ (Markdown: https://insights.sbomify.com/CVE-2026-32104/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32104
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32104
- OSV: https://osv.dev/vulnerability/CVE-2026-32104

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32104/
Summaries are generated and may contain mistakes; the official description above is the record.