{"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-24134 exists.","fix":"Upgrade studiocms to 0.2.0 or later.","what":"CVE-2026-24134 is a medium-severity missing authorization vulnerability in withstudiocms studiocms, published on 27 Jan 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-24134 and fix it if it is affected.\n\nWhat it is: CVE-2026-24134 is a medium-severity missing authorization vulnerability in withstudiocms studiocms, published on 27 Jan 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-24134 exists.\n\nAffected packages and fixed versions:\n- studiocms (npm): affected all versions; fixed in 0.2.0\n- studiocms (npm): affected all versions; fixed in 0.2.0\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-24134/ (Markdown: https://insights.sbomify.com/CVE-2026-24134/index.md)","id":"CVE-2026-24134","markdown":"https://insights.sbomify.com/CVE-2026-24134/index.md","name":"CVE-2026-24134","record":{"aliases":["GHSA-8cw6-53m5-4932"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"StudioCMS headless CMS","requires_auth":"low_privilege","summary":"Visitors can access draft content created by privileged users due to missing authorization checks in StudioCMS.","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":6.5,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N","version":"3.1"},"cwes":[{"id":"CWE-862","name":"Missing Authorization"},{"id":"CWE-639","name":"Authorization Bypass Through User-Controlled Key"}],"description":"StudioCMS is a server-side-rendered, Astro native, headless content management system. Versions prior to 0.2.0 contain a Broken Object Level Authorization (BOLA) vulnerability in the Content Management feature that allows users with the \"Visitor\" role to access draft content created by Editor/Admin/Owner users. Version 0.2.0 patches the issue.","ecosystems":["npm"],"exploits":{"exploitdb":0,"first_seen":"2026-01-29","github_poc":1,"max_poc_stars":0,"metasploit":0,"nuclei":0,"refs":[{"date":"2026-01-29T21:03:34Z","kind":"github_poc","ref":"https://github.com/FilipeGaudard/CVE-2026-24134-PoC","stars":0,"title":null}],"tier":"weaponised"},"has_fix":true,"headline":"StudioCMS has an Authorization Bypass Through User-Controlled Key","id":"CVE-2026-24134","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":"npm","product":null,"products":[],"type":"missing_authorization","year":"2026"},"n_packages":2,"n_references":3,"next":{"headline":"Gogs vulnerable to arbitrary file deletion via path traversal in wiki page update","id":"CVE-2026-24135"},"packages":[{"ecosystem":"npm","fixed":["0.2.0"],"introduced":["0"],"last_affected":[],"package":"studiocms","purl":null,"source":"GHSA-8cw6-53m5-4932"},{"ecosystem":"npm","fixed":["0.2.0"],"introduced":["0"],"last_affected":[],"package":"studiocms","purl":"pkg:npm/studiocms","source":"GHSA-8cw6-53m5-4932"}],"prev":{"headline":"jsPDF Affected by Denial of Service (DoS) via Unvalidated BMP Dimensions in BMPDecoder","id":"CVE-2026-24133"},"products":["studiocms"],"published":"2026-01-27","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":5.4,"headline":"StudioCMS: IDOR in User Notification Preferences Allows Any Authenticated User to Modify Any User's Settings","id":"CVE-2026-32104","kev_date_added":null,"published":"2026-03-11"},{"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)"},{"class":"open","licence":"CC0","name":"PoC-in-GitHub"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-01-28","vendors":["withstudiocms"]},"summary":"Visitors can access draft content created by privileged users due to missing authorization checks in StudioCMS.","url":"https://insights.sbomify.com/CVE-2026-24134/"}