CVE-2026-24134

StudioCMS has Authorization Bypass Through User-Controlled Key

Impact Scenarios:

1. Information Disclosure:

   • Visitor users can read unpublished drafts containing sensitive information
   • Drafts may contain confidential business information, unreleased announcements, or proprietary content
   • Competitive intelligence could be gathered from draft content

2. Privacy Violation:

   • Personal notes, work-in-progress content, or internal communications in drafts exposed
   • Violation of content creator privacy expectations

3. Business Impact:

   • Premature disclosure of marketing campaigns, product launches, or announcements
   • Loss of competitive advantage if draft strategies are exposed
   • Potential compliance issues if drafts contain regulated information

4. Complete RBAC Bypass:

   • The entire role-based access control system for draft content is bypassed
   • "Visitor" role becomes equivalent to "Editor" for read access to drafts
   • Undermines the trust model of multi-user content management

The application does not perform an authorization check before performing a sensitive operation. Typical impact: unauthorized access to restricted functionality or data.

CVE-2026-24134 has a CVSS score of 6.5 (Medium). The vector is network-reachable, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (0.2.0); upgrading removes the vulnerable code path.

Kodem intelligence

1. What is CVE-2026-24134? CVE-2026-24134 is a medium-severity missing authorization vulnerability in studiocms (npm), affecting versions < 0.2.0. It is fixed in 0.2.0. The application does not perform an authorization check before performing a sensitive operation.
2. How severe is CVE-2026-24134? CVE-2026-24134 has a CVSS score of 6.5 (Medium). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which versions of studiocms are affected by CVE-2026-24134? studiocms (npm) versions < 0.2.0 is affected.
4. Is there a fix for CVE-2026-24134? Yes. CVE-2026-24134 is fixed in 0.2.0. Upgrade to this version or later.
5. Is CVE-2026-24134 exploitable, and should I be worried? Whether CVE-2026-24134 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2026-24134 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2026-24134? Upgrade studiocms to 0.2.0 or later.