TI-2026-25147 Aliases CVE-2026-32638 GHSA-xvf4-ch4q-2m24

StudioCMS REST getUsers Exposes Owner Account Records to Admin Tokens

MEDIUM 47CWE-639Published 2026-03-18 · Updated 2026-03-19

Key facts

Attack vector: Network
Privileges required: High
User interaction: None
Attack complexity: Low
Impact type: Security bypass
Confidentiality · integrity · availability: Low · None · None
Fix status: Fixed

Attack profile from CVSS 3.1 · CNA. Fix status from CNA and GitHub. Impact type from CWE-639.

Summary

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.

Why it matters now

Exploitation Proof of concept CISA SSVC · not in CISA KEV

EPSS 0.00398 34th percentileScored 2026-11-07

Public exploit Yes 1 exploit referenceTagged by NVD

Fix Fixed studiocms (withstudiocms): 0.4.4studiocms (npm): 0.4.4

SSVC decision points

CISA ADP · SSVC 2.0.3

Exploitation: Poc
Automatable: No
Technical impact: Partial

The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.

Affected products

Vendor	Product	Affected versions	Fixed in	Status	Source
withstudiocms	studiocms	before 0.4.4	0.4.4	Patch available	CNA
—	studiocms (npm)	before 0.4.4	0.4.4	Patch available	GHSA-xvf4-ch4q-2m24

studiocms Vendorwithstudiocms Affected before 0.4.4 Fixed in 0.4.4 Patch available CNA
studiocms (npm) Vendor— Affected before 0.4.4 Fixed in 0.4.4 Patch available GHSA-xvf4-ch4q-2m24

CPE configurations NVD · 1

CPE	Versions	Role	Vendor
cpe:2.3:a:studiocms:studiocms::::::::	before 0.4.4	Vulnerable	withstudiocms

cpe:2.3:a:studiocms:studiocms:*:*:*:*:*:*:*:* Versions before 0.4.4 Vulnerable ·withstudiocms

Remediation

Fix · CNA studiocms (withstudiocms) Fixed in 0.4.4
Fix · GHSA-xvf4-ch4q-2m24 studiocms (npm) Fixed in 0.4.4 Advisory →

Timeline

2026-10-02 Threatist record created from CVE-2026-32638
2026-10-03 Alias added: GHSA-xvf4-ch4q-2m24

References

Other 2

TI-2026-23769 StudioCMS Affected by Privilege Escalation via Insecure API Token Generation CVSS 3.1HIGH 8.8
TI-2026-24639 StudioCMS S3 Storage Manager Authorization Bypass via Missing `await` on Async Auth Check CVSS 3.1HIGH 7.6
TI-2026-24644 StudioCMS: REST API Missing Rank Check Allows Admin to Create Peer Admin Accounts CVSS 3.1HIGH 7.2
TI-2026-24641 StudioCMS: IDOR — Admin-to-Owner Account Takeover via Password Reset Link Generation CVSS 3.1HIGH 7.2
TI-2026-19452 StudioCMS has an Authorization Bypass Through User-Controlled Key CVSS 3.1MEDIUM 6.5
TI-2026-24642 StudioCMS: IDOR in User Notification Preferences Allows Any Authenticated User to Modify Any User's Settings CVSS 3.1MEDIUM 5.4

See all 7 →

Sources

This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences