VulnerabilityPublished 18 Mar 2026

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

Affects withstudiocms studiocmsSource CVE Database V5

Compare

Not known to be exploited · CVSS 2.7 Low : upgrade to 0.4.4 when convenient.

Data as of 31 Oct 2026, 08:20 UTC

CVSS 3.1 base score

2.7Low

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

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

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: High
User Interaction: None
Scope: Unchanged
Confidentiality: Low
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: High: The attacker is authorized with (i.e., requires) privileges that provide significant (e.g., administrative) control over the vulnerable component that could affect component-wide settings and files.
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: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the impacted component.
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 18 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: 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 30 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.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), 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.4.4.

Affected software

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

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

AI-suggested

Organizations should upgrade StudioCMS to version 0.4.4 or later, where the authorization bypass issue is fixed. Until upgrading, administrators should restrict admin token issuance and monitor admin API usage for suspicious queries involving the 'rank' parameter. Implement additional logging and alerting on access to owner-level user data to detect potential abuse. Review and audit all user management API endpoints for consistent authorization enforcement to prevent similar inconsistencies. Employ the principle of least privilege by limiting admin roles to only necessary permissions and consider multi-factor authentication to reduce risk of admin token compromise. If custom integrations or API clients exist, verify they do not rely on the vulnerable getUsers endpoint behavior. Finally, maintain an incident response plan to address potential insider threats or misuse of admin privileges.

Description

CVE-2026-32638 is an authorization bypass vulnerability in StudioCMS versions prior to 0.4.4. The REST API's getUsers endpoint improperly uses an attacker-controlled 'rank' query parameter to filter user accounts, allowing admin users to retrieve owner account details such as IDs, usernames, display names, and email addresses. This occurs despite the adjacent getUser endpoint correctly restricting access to owner user data, indicating an authorization inconsistency within the same user management interface. The vulnerability has a low CVSS score of 2.7, reflecting limited impact and the requirement for admin privileges to exploit. No known exploits are currently reported in the wild. The issue is resolved in StudioCMS version 0.4.

Impact

The primary impact of this vulnerability is unauthorized disclosure of owner account information to users with admin privileges. While admin users typically have elevated access, owner accounts may represent a higher trust level or contain more sensitive information. Exposure of owner usernames, email addresses, and IDs could facilitate targeted phishing, social engineering, or further privilege escalation attempts if combined with other vulnerabilities. However, since exploitation requires an admin token, the risk is limited to insiders or compromised admin accounts. There is no impact on data integrity or system availability. Organizations using vulnerable versions of StudioCMS risk leaking sensitive user data within their administrative user base, which could undermine trust and compliance with data protection policies. The lack of known exploits in the wild reduces immediate threat but patching is recommended to maintain proper authorization controls and prevent potential misuse.

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).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 26 Mar 2026, 01:13 UTC

WeaknessesCWE-639

Technical details

References

Community reviews

Related threats