Quick answers
- Is CVE-2026-32104 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-32104 being exploited in the wild.
- How severe is CVE-2026-32104?
- Low severity, with a CVSS score of 3.1, published 12 March 2026.
- Which products and versions are affected?
- studiocms (npm) SEMVER:introduced=0,fixed=0.4.3.
- Is there a fix for CVE-2026-32104?
- Yes. studiocms (npm): upgrade to 0.4.3 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-32104 attacked?
- It is attacked over the network.
- Am I affected by CVE-2026-32104?
- Check whether you run studiocms (npm) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- studiocms (npm): upgrade to 0.4.3 or later
npm install studiocms@0.4.3
Technical details
The vulnerability is an Insecure Direct Object Reference (IDOR) in the updateUserNotifications endpoint (CWE-639). The endpoint accepts a user ID in the request payload and updates that user's notification preferences, but only checks that the caller is authenticated—it never verifies ownership of the target account. The vulnerable code at packages/studiocms/frontend/pages/studiocms_api/_handlers/dashboard/users.ts:257-311 uses the attacker-controlled ID parameter directly instead of using the logged-in user's ID. Any authenticated visitor (low privilege) can exploit this via a simple POST request to disable notifications for admin accounts, suppressing detection of follow-on attacks. The fix is to add an ownership check unless the caller is an admin.
Affected products
- StudioCMS StudioCMS <=0.4.2
Identifiers
- CVE-2026-32104
- GHSA-9v82-xrm4-mp52
Timeline
- 2026-03-12: disclosed: Advisory published
- 2026-03-12: patched: Fixed in version 0.4.3