Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 5.4amended

StudioCMS: IDOR in User Notification Preferences Allows Any Authenticated User to Modify Any User's Settings

CVE-2026-32104GHSA-9v82-xrm4-mp52

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (studiocms 0.4.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L
EPSS
  • CVE-2026-32104: 0.27% estimated exploitation activity in the next 30 days; percentile 19.08 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary 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. Details The vulnerable handler is in packages/studiocms/frontend/pages/studiocmsapi/handlers/dashboard/users.ts:257-311: For comparison, the updateUserProfile handler in dashboard/profile.ts correctly uses userData.user.id instead of a user-supplied ID, preventing IDOR. PoC Impact - Any authenticated visitor can disable notification preferences for admin/owner accounts, suppressing alerts about new user creation, account changes, and user deletions - Enables attack chaining — suppress admin notifications first, then perform other malicious actions with…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-9v82-xrm4-mp52

  2. Revision 1 · created ·

    Published from osv record GHSA-9v82-xrm4-mp52

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32104

Advisory: StudioCMS: IDOR in User Notification Preferences Allows Any Authenticated User to Modify Any User's Settings
IDs: CVE-2026-32104, GHSA-9v82-xrm4-mp52
Record: https://patchnext.com/advisories/cve-2026-32104 (revision 2, source checked 26 Oct 2026, 12:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: studiocms 0.4.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm studiocms: affected <= 0.4.2; fixed in 0.4.3

## Suggested inspection (read-only)
- `npm ls studiocms --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on studiocms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-9v82-xrm4-mp52 (OSV record GHSA-9v82-xrm4-mp52 lists affected ranges: npm studiocms >=0 <0.4.3 (fixed))
- Verified: https://github.com/advisories/GHSA-9v82-xrm4-mp52 (GitHub-reviewed advisory GHSA-9v82-xrm4-mp52 lists affected ranges: npm studiocms >=0 <=0.4.2)

Commands are suggestions: review each one before running it.

Loading voting…