CVE-2026-24134: StudioCMS Authorization Bypass Vulnerability in Content Management

studiocms Updated 28 Jan 2026

Summary

27/01/2026
Yes i
Moderate
6.5

CVE-2026-24134: StudioCMS has Authorization Bypass Through User-Controlled Key. Affects studiocms versions < 0.2.0. Fixed in 0.2.0. How to fix ↓

Free scan

Check if this vulnerability affects your application

Upload a manifest or SBOM and we'll show whether you're affected, plus every other risky package in the same scan.

Check my app free

No signup required · Results in about 60 seconds

Upload your dependency manifest or SBOM

Drag & drop your file here or

Java Javascript PHP Python Go Rust Ruby Dart C/C++ Elixir CycloneDX SPDX

Upload a supported dependency manifest or SBOM. No installation or source-code access required.

See supported files and SBOM formats
SBOM sbom.json · bom.json · bom.xml · *.spdx.json · *.cdx.json · *.cdx.xml
Java pom.xml · gradle.lockfile · buildscript-gradle.lockfile
Javascript package-lock.json · yarn.lock · pnpm-lock.yaml
PHP composer.lock
Python poetry.lock · requirements.txt · Pipfile.lock
Go go.mod
Rust Cargo.lock
Ruby Gemfile.lock
Dart pubspec.lock
C/C++ conan.lock
Elixir mix.lock
Enter your work email to receive your report link.

Verify your email to view the full report and start 30 days of continuous monitoring. No credit card required.

Sponsored Devnack Mobile apps built by Devnack Design, build and launch iOS and Android apps with a senior product team. From idea to store release Start a project

Background

StudioCMS is an open-source content management system designed to facilitate the creation, editing, and management of digital content. It offers various user roles, including Editor, Admin, Owner, and Visitor, each with different levels of access and permissions. The system is widely used for managing websites and applications, but it has a critical vulnerability that allows unauthorized access to sensitive draft content.

Vulnerability Detail

StudioCMS contains a Broken Object Level Authorization (BOLA) vulnerability in its Content Management feature. This issue arises because the system fails to validate user roles and content ownership when accessing draft content. Specifically, users with the 'Visitor' role can access drafts created by users with higher privileges (Editor, Admin, Owner) by manipulating the URL to include the UUID of the draft. This flaw can lead to information disclosure, privacy violations, and potential business impacts, as sensitive and unpublished content may be exposed to unauthorized users.

How To Fix

Latest published version: 0.7.0 as of 22 Oct 2026

npm install studiocms@0.7.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.2.0

This is the first release that contains the fix.

npm install studiocms@0.2.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Workaround

As a temporary workaround, restrict access to the content management dashboard by implementing additional server-side checks to validate user roles and content ownership before allowing access to draft content. This can be done by modifying the endpoint logic to ensure that only users with the appropriate roles can access specific drafts.

Conclusion

The CVE-2026-24134 vulnerability in StudioCMS poses a significant risk by allowing unauthorized access to draft content. It is crucial for users to update to the patched version and implement additional security measures to safeguard sensitive information.

See every vulnerability recorded for studiocms →

Share this vulnerability

FAQ

The vulnerability is a Broken Object Level Authorization (BOLA) issue that allows unauthorized users to access draft content.

Users with the 'Visitor' role in StudioCMS are primarily affected, as they can access drafts created by higher-privileged users.

The impacts include information disclosure, privacy violations, and potential business risks due to the exposure of sensitive content.

You can use Vulert's playground at Vulert Scanner to check if your application is affected by this vulnerability without needing to sign up.

The CVSS score of this vulnerability is 6.5, indicating a moderate severity level.

Related vulnerabilities

Recent vulnerabilities recorded for studiocms.

How To Fix

Latest published version: 0.7.0 as of 22 Oct 2026

npm install studiocms@0.7.0

Upgrading to it may include breaking changes; the version below is the minimum fixed release for this vulnerability.

If you need the minimum change

0.2.0

This is the first release that contains the fix.

npm install studiocms@0.2.0

Tip — Not sure which version your app runs? Vulert can match this fix to it. Scan free →

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →
Help improve this record
Report an issue or send feedback