VulnerabilityPublished 27 Jan 2026

CVE-2026-24134: withstudiocms studiocms · Insecure Direct Object Reference

Affects withstudiocms studiocmsSource CVE Database V5

Not known to be exploited · CVSS 6.5 Medium : upgrade to 0.2.0 when convenient.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score

6.5Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.3% chance of exploitation in 30 days – higher than 27% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 0.2.0

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Attack Vector: Network
Attack Complexity: Low
Privileges Required: Low
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: None
Availability: None

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: Low: The attacker is authorized with (i.e., requires) privileges that provide basic user capabilities that could normally affect only settings and files owned by a user. Alternatively, an attacker with Low privileges may have the ability to cause an impact only to non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 27 Jan 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Upgrade studiocms and withstudiocms/studiocms to 0.2.0.

Affected software

Product	Affected	Fixed in
withstudiocmsstudiocms	Affected <0.2.0	Fixed in 0.2.0
GitHubwithstudiocms/studiocms`pkg:github/withstudiocms/studiocms`Other threats	Affected <0.2.0	Fixed in 0.2.0

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To effectively mitigate CVE-2026-24134, European organizations should: 1) Immediately upgrade StudioCMS to version 0.2.0 or later, where the vulnerability is patched. 2) Conduct an audit of user roles and permissions within StudioCMS to ensure the 'Visitor' role is assigned only to trusted users and that no unnecessary privileges are granted. 3) Implement strict access control policies and monitor access logs for unusual activity involving draft content retrieval. 4) Employ network segmentation and zero-trust principles to limit access to the CMS backend, reducing the risk from compromised low-privilege accounts. 5) Where possible, enable multi-factor authentication (MFA) for all CMS users to reduce the risk of account compromise. 6) Review and sanitize draft content to minimize sensitive information exposure in case of unauthorized access. 7) Establish an incident response plan specific to CMS content breaches to quickly address any unauthorized disclosures. 8) Stay informed on updates from the vendor and security advisories related to StudioCMS.

Description

CVE-2026-24134 is a Broken Object Level Authorization (BOLA) vulnerability in StudioCMS versions prior to 0.2.0. It allows users with the 'Visitor' role to access draft content created by higher-privileged users such as Editors, Admins, or Owners. The vulnerability arises from improper authorization checks on user-controlled keys in the content management feature. Exploitation requires no user interaction but does require low-level privileges (Visitor role). The vulnerability impacts confidentiality by exposing sensitive unpublished content but does not affect integrity or availability. The issue is patched in version 0.2.0.

Impact

For European organizations, the primary impact of CVE-2026-24134 is the unauthorized disclosure of sensitive draft content within StudioCMS. This can lead to premature exposure of confidential information, intellectual property, or strategic communications before official release, potentially damaging reputation and competitive advantage. Media companies, marketing agencies, and enterprises relying on StudioCMS for content management are particularly at risk. Although the vulnerability does not compromise data integrity or system availability, the breach of confidentiality can violate data protection regulations such as GDPR if personal or sensitive data is exposed. Additionally, unauthorized access to draft content may facilitate further social engineering or targeted attacks. The requirement of a 'Visitor' role for exploitation limits the attack surface to authenticated users with minimal privileges, but insider threats or compromised low-privilege accounts could leverage this vulnerability. The absence of known exploits reduces immediate risk but does not eliminate the potential for future attacks. Organizations should prioritize patching and review access controls to mitigate exposure.

CWE-639Authorization Bypass Through User-Controlled Key (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #24OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
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.
Architecture and Design
For each and every data access, ensure that the user has sufficient privilege to access the record that is being requested.
Architecture and Design · Implementation
Make sure that the key that is used in the lookup of a specific user's record is not controllable externally by the user or that any tampering can be detected.
Architecture and Design
Use encryption in order to make it more difficult to guess other legitimate values of the key or associate a digital signature with the key so that the server can verify that there has been no tampering.
OWASP Cheat Sheets
Access Control (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V4.1.2 (opens in a new tab)
V4.2.1 (opens in a new tab)
V8.3.8 (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).
CWE-862Missing Authorization (opens in a new tab)
Class weaknessLikelihood of exploit: HighCWE Top 25 (2025): #4OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The product does not perform an authorization check when an actor attempts to access a resource or perform an action.
Architecture and Design
Divide the product into anonymous, normal, privileged, and administrative areas. Reduce the attack surface by carefully mapping roles with data and functionality. Use role-based access control (RBAC) to enforce the roles at the appropriate boundaries.
Architecture and Design
Ensure that access control checks are performed related to the business logic. These checks may be different than the access control checks that are applied to more generic resources such as files, connections, processes, memory, and database records.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
OWASP Cheat Sheets
Authorization (opens in a new tab)
OWASP ASVS 4.0.3
V8.3.8 (opens in a new tab)
V13.4.2 (opens in a new tab)
V7.2.2 (opens in a new tab)
Attack patterns
Exploitation of Thunderbolt Protection Flaws (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 4 Feb 2026, 09:24 UTC

WeaknessesCWE-639, CWE-862

Technical details

References

Community reviews

Related threats