CVE-2026-32638
StudioCMS is a server-side-rendered, Astro native, headless content management system.
Published Mar 18, 2026 · updated Jun 17, 2026 · studiocms studiocms
StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.4, the REST API endpoint in StudioCMS uses the attacker-controlled query parameter to decide whether owner accounts should be filtered from the result set. As a result, an admin token can request and receive owner account records, including IDs, usernames, display names, and email addresses, even though the adjacent 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.
Code
The project this record applies to. Exploit listings stay in References.
Timeline
Detection, updates, and resolution for this record.
Mar 18, 2026 · NIST NVD
Detected
StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.4, the REST API endpoint in StudioCMS uses the attacker-controlled query parameter to decide whether owner accounts should be filtered from the result set. As a result, an admin token can request and receive owner account records, including IDs, usernames, display names, and email addresses, even th
Jun 17, 2026 · NIST NVD
Updated
StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.4, the REST API endpoint in StudioCMS uses the attacker-controlled query parameter to decide whether owner accounts should be filtered from the result set. As a result, an admin token can request and receive owner account records, including IDs, usernames, display names, and email addresses, even th
Affected
- cpe studiocms/studiocmsversion unspecified
Sources
- CVE.orgVulnerability recordCVE-2026-32638
Official CVE identifier
cve.org - NIST NVDVulnerability recordCVE-2026-32638
StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.4, the REST API endpoint in StudioCMS uses the attacker-controlled query parameter to decide whether owner accounts should be filtered from the result set. As a r
nvd.nist.gov