Vulnerability · Published Mar 11, 2026 · Assigned by GitHub_M

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

Medium 5.4

In plain English

A medium-severity authorization bypass via user-controlled key in studiocms from withstudiocms. Proof-of-concept exploit code is public. The chance it is exploited in the next 30 days is estimated at 0.3% (higher than 21% of all known vulnerabilities). Fixed versions are available - upgrade the affected package.

Severity (CVSS 3.1)5.4Medium

Exploit odds (30 days)0.3%top 78.9% of all CVEs

Exploited in the wildNo reportsCISA SSVC: poc

Attack toolingNoneno public tooling known

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.

Affected packages & fixed versions

Ecosystem	Package	Fixed in	Advisory
npm	studiocms	0.4.3	GHSA-9v82-xrm4-mp52

Affected products (as reported)

Vendor	Product	Versions
withstudiocms	studiocms	< 0.4.3

Weakness: CWE-639 · Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L

References

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