CVE-2026-32638

LOW EPSS 29.3%
Published Mar 18, 20263mo ago · Modified Mar 19, 20263mo ago
2.7 CVSS 3.1
Low
Find Similar
Published Mar 18, 2026 3mo ago
Last Modified Mar 19, 2026 3mo ago

Description

StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.4, the REST API `getUsers` endpoint in StudioCMS uses the attacker-controlled `rank` query parameter to decide whether owner accounts should be filtered from the result set. As a result, an admin token can request `rank=owner` and receive owner account records, including IDs, usernames, display names, and email addresses, even though the adjacent `getUser` endpoint correctly blocks admins from viewing owner users. This is an authorization inconsistency inside the same user-management surface. Version 0.4.4 fixes the issue.

CVSS Details

Base Score
2.7
Exploitability
1.2
Impact
1.4
Vector string
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

Threat Intelligence

EPSS Exploit Probability
29.3% percentile
Exploit & Patch Status
Public Exploit Known
Patch Available

Weaknesses 1

CWE-639

Affected Products 1

VendorProductVersionRange
studiocmsstudiocms* <0.4.4

References 3

  • github.com https://github.com/withstudiocms/studiocms/commit/aebe8bcb3618bb07c6753e3f5c982c1fe6adea64
    Patch
  • github.com https://github.com/withstudiocms/studiocms/releases/tag/studiocms@0.4.4
    ProductRelease Notes
  • github.com https://github.com/withstudiocms/studiocms/security/advisories/GHSA-xvf4-ch4q-2m24
    ExploitMitigationVendor Advisory

Remediation

  • github.com https://github.com/withstudiocms/studiocms/commit/aebe8bcb3618bb07c6753e3f5c982c1fe6adea64
    Patch