{"answers":{"affected":"2 open source packages ship an affected version, including studiocms. It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32104 exists.","fix":"Upgrade studiocms to 0.4.3 or later.","what":"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."},"fix_prompt":"Check this codebase for CVE-2026-32104 and fix it if it is affected.\n\nWhat 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.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32104 exists.\n\nAffected packages and fixed versions:\n- studiocms (npm): affected all versions; fixed in 0.4.3\n- studiocms (npm): affected all versions; fixed in 0.4.3\n\nTask:\n1. 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.\n2. 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.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2026-32104/ (Markdown: https://insights.sbomify.com/CVE-2026-32104/index.md)","id":"CVE-2026-32104","markdown":"https://insights.sbomify.com/CVE-2026-32104/index.md","name":"CVE-2026-32104","record":{"aliases":["GHSA-9v82-xrm4-mp52"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"StudioCMS","requires_auth":"low_privilege","summary":"Authenticated users can modify any other user's notification settings, potentially disabling admin alerts to hide malicious activity.","user_interaction":"not_required","vuln_class":"missing_authorization"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"studiocms","vendor":"studiocms"}],"cvss":{"score":5.4,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:L","version":"3.1"},"cwes":[{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"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.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":true,"headline":"StudioCMS: IDOR in User Notification Preferences Allows Any Authenticated User to Modify Any User's Settings","id":"CVE-2026-32104","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":1,"next":{"headline":"xrdp: RDP MAC signature (dataSignature) never verified on receive — integrity bypass in non-TLS mode","id":"CVE-2026-32105"},"packages":[{"ecosystem":"npm","fixed":["0.4.3"],"introduced":["0"],"last_affected":[],"package":"studiocms","purl":null,"source":"GHSA-9v82-xrm4-mp52"},{"ecosystem":"npm","fixed":["0.4.3"],"introduced":["0"],"last_affected":[],"package":"studiocms","purl":"pkg:npm/studiocms","source":"GHSA-9v82-xrm4-mp52"}],"prev":{"headline":"StudioCMS: IDOR — Admin-to-Owner Account Takeover via Password Reset Link Generation","id":"CVE-2026-32103"},"products":["studiocms"],"published":"2026-03-11","related":[{"cvss_score":8.8,"headline":"StudioCMS Affected by Privilege Escalation via Insecure API Token Generation","id":"CVE-2026-30944","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":7.6,"headline":"StudioCMS S3 Storage Manager Authorization Bypass via Missing `await` on Async Auth Check","id":"CVE-2026-32101","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":7.1,"headline":"StudioCMS: IDOR — Arbitrary API Token Revocation Leading to Denial of Service","id":"CVE-2026-30945","kev_date_added":null,"published":"2026-03-10"},{"cvss_score":6.8,"headline":"StudioCMS: IDOR — Admin-to-Owner Account Takeover via Password Reset Link Generation","id":"CVE-2026-32103","kev_date_added":null,"published":"2026-03-11"},{"cvss_score":6.5,"headline":"StudioCMS has an Authorization Bypass Through User-Controlled Key","id":"CVE-2026-24134","kev_date_added":null,"published":"2026-01-27"},{"cvss_score":4.7,"headline":"StudioCMS: REST API Missing Rank Check Allows Admin to Create Peer Admin Accounts","id":"CVE-2026-32106","kev_date_added":null,"published":"2026-03-11"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CC BY 4.0","name":"GitHub Advisory Database","prefix":"GHSA"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-03-12","vendors":["withstudiocms"]},"summary":"Authenticated users can modify any other user's notification settings, potentially disabling admin alerts to hide malicious activity.","url":"https://insights.sbomify.com/CVE-2026-32104/"}