How severe is CVE-2026-32104?

CVE-2026-32104 has a CVSS 3.x base score of 5.4, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability low.

Is CVE-2026-32104 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (17th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-32104?

CVE-2026-32104 affects Studiocms. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-32104?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

Does CVE-2026-32104 have an EU (EUVD) identifier?

Yes. CVE-2026-32104 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-11373.

When was CVE-2026-32104 published?

CVE-2026-32104 was published on 2026-03-11 and last updated on 2026-06-17.

CVE-2026-32104

CVE-2026-32104 is a medium-severity vulnerability in Studiocms with a CVSS 3.x base score of 5.4. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-639.

Key facts

Severity: Medium (CVSS 3.x base score 5.4)
EPSS exploit prediction: 0% (17th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-11373
Weakness: CWE-639
Affected product: Studiocms
Published: 2026-03-11
Last modified: 2026-06-17

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.

Frequently asked questions

What is CVE-2026-32104?: 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.
How severe is CVE-2026-32104?: CVE-2026-32104 has a CVSS 3.x base score of 5.4, rated medium severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability low.
Is CVE-2026-32104 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (17th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-32104?: CVE-2026-32104 affects Studiocms. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-32104?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
Does CVE-2026-32104 have an EU (EUVD) identifier?: Yes. CVE-2026-32104 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-11373.
When was CVE-2026-32104 published?: CVE-2026-32104 was published on 2026-03-11 and last updated on 2026-06-17.

References

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

Affected products (1)

cpe:2.3:a:studiocms:studiocms:*:*:*:*:*:*:*:*

More vulnerabilities in Studiocms

CVE-2026-30944 — High (CVSS 8.8): StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.0, the…
CVE-2026-32101 — High (CVSS 7.6): StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.3.1, the S3 storage…
CVE-2026-30945 — High (CVSS 7.1): StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.0, the DELETE…
CVE-2026-32103 — Medium (CVSS 6.8): StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.3, the POST…
CVE-2026-24134 — Medium (CVSS 6.5): StudioCMS is a server-side-rendered, Astro native, headless content management system. Versions prior to 0.2.0 contain…
CVE-2026-32106 — Medium (CVSS 4.7): StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.3, the REST API…

All CVEs affecting Studiocms →

Other CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities

CVE-2025-40805 — Critical (CVSS 10.0): Affected devices do not properly enforce user authentication on specific API endpoints. This could facilitate an…
CVE-2024-45032 — Critical (CVSS 10.0): A vulnerability has been identified in Industrial Edge Management Pro (All versions < V1.9.5), Industrial Edge…
CVE-2026-34037 — Critical (CVSS 9.9): Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to…
CVE-2026-52782 — Critical (CVSS 9.9): OpenProject is open-source, web-based project management software. Prior to 17.3.3 and 17.4.1, there is an IDOR through…
CVE-2026-45552 — Critical (CVSS 9.9): Roxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepalived servers. In versions 8.2.6.4 and prior,…
CVE-2026-29200 — Critical (CVSS 9.9): A critical IDOR vulnerability has been discovered in Comet Backup affecting all versions from 20.11.0 to 26.1.1 and…

Browse all CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities →