NewApp Monitoring is liveSign up free
AgentbeamBeta
Open-source package vulnerability · npm

CVE-2026-24134: StudioCMS has Authorization Bypass Through User-Controlled Key

mediumCVSS 3.1 6.5GHSA-8cw6-53m5-4932

Summary StudioCMS contains 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. Details The Issue: The endpoint /dashboard/content-management/edit?edit={UUID} validates user authentication but does NOT validate: 1. User role (should require Editor/Admin/Owner) 2.

Published Jan 27, 2026 · Updated Jan 29, 2026

Affected packages

studiocms

Ecosystem
npm
Affected
< 0.2.0
Fixed in
0.2.0
Check
npm ls studiocms

Advisory details

From the GitHub Advisory Database (CC BY 4.0).

Summary

StudioCMS contains 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.

Details

The Issue: The endpoint /dashboard/content-management/edit?edit={UUID} validates user authentication but does NOT validate:

  1. User role (should require Editor/Admin/Owner)
  2. Content ownership (should verify the draft belongs to the user)

This allows users with "Visitor" role (lowest privilege) to access draft content created by Editor/Admin/Owner users by directly accessing the edit URL with the content UUID.

PoC

  • User A: Editor role (example username: dummy04)
  • User B: Visitor role (example username: dummy01)

Reproduction Steps:

Step 1 - Create draft as Editor:

  1. Login as User A (Editor role)
  2. Navigate to: http://localhost:4321/dashboard/content-management
  3. Create new content (it will stay as draft)
  4. After saving, note the UUID in the URL:
   http://localhost:4321/dashboard/content-management/edit?edit=bad87630-69a4-4cd6-bcb2-6965839dc148

Copy this UUID: bad87630-69a4-4cd6-bcb2-6965839dc148

Step 2 - Access draft as Visitor:

  1. Login as Visitor and get auth_session cookie
curl -X POST "http://127.0.0.1:4321/studiocms_api/auth/login" -F 'username=dummy01' -F 'password=dummy01pass$'
  1. Proof of Visitor permission
  1. Access Editor's draft using the UUID
curl "http://127.0.0.1:4321/dashboard/content-management/edit?edit=bad87630-69a4-4cd6-bcb2-6965839dc148" -H "Cookie: auth_session=qvawh6zv23hc2spu6xx7pzgrnn4rpd3q" -v

Result: Returns full HTML page with draft content (200 OK)

Impact

Impact Scenarios:

  1. Information Disclosure:
  2. Visitor users can read unpublished drafts containing sensitive information
  3. Drafts may contain confidential business information, unreleased announcements, or proprietary content
  4. Competitive intelligence could be gathered from draft content
  1. Privacy Violation:
  2. Personal notes, work-in-progress content, or internal communications in drafts exposed
  3. Violation of content creator privacy expectations
  1. Business Impact:
  2. Premature disclosure of marketing campaigns, product launches, or announcements
  3. Loss of competitive advantage if draft strategies are exposed
  4. Potential compliance issues if drafts contain regulated information
  1. Complete RBAC Bypass:
  2. The entire role-based access control system for draft content is bypassed
  3. "Visitor" role becomes equivalent to "Editor" for read access to drafts
  4. Undermines the trust model of multi-user content management

Credited to FilipeGaudard, Adammatthiesen.

References

How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. No analysis has been written for this entry yet. Methodology

More npm vulnerabilities

All npm entries