Skip to content

StudioCMS has Authorization Bypass Through User-Controlled Key

Moderate severity GitHub Reviewed Published Jan 27, 2026 in withstudiocms/studiocms • Updated Jan 29, 2026

Package

npm studiocms (npm)

Affected versions

< 0.2.0

Patched versions

0.2.0

Description

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$'

01

  1. Proof of Visitor permission

02

  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:

    • 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

References

@Adammatthiesen Adammatthiesen published to withstudiocms/studiocms Jan 27, 2026
Published to the GitHub Advisory Database Jan 27, 2026
Reviewed Jan 27, 2026
Published by the National Vulnerability Database Jan 28, 2026
Last updated Jan 29, 2026

Severity

Moderate

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(8th percentile)

Weaknesses

Authorization Bypass Through User-Controlled Key

The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. Learn more on MITRE.

Missing Authorization

The product does not perform an authorization check when an actor attempts to access a resource or perform an action. Learn more on MITRE.

CVE ID

CVE-2026-24134

GHSA ID

GHSA-8cw6-53m5-4932

Credits

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.