# CVE-2026-32638: StudioCMS REST getUsers Exposes Owner Account Records to Admin Tokens

> Admin tokens can bypass authorization checks to view owner account details via the getUsers endpoint, exposing sensitive user information.

- **Severity:** Low 2.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Mar 2026
- **Updated:** 19 Mar 2026
- **Also known as:** GHSA-xvf4-ch4q-2m24

## What is CVE-2026-32638?

CVE-2026-32638 is a low-severity missing authorization vulnerability in withstudiocms studiocms, published on 18 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official 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.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

## Which versions are affected by CVE-2026-32638?

2 open source packages ship an affected version, including studiocms. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `studiocms` | npm | All versions | 0.4.4 |
| `studiocms` | npm | All versions | 0.4.4 |

Products: Studiocms Studiocms.

## How do I fix CVE-2026-32638?

Upgrade studiocms to 0.4.4 or later.

## Is CVE-2026-32638 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32638 exists.

## Other vulnerabilities in withstudiocms studiocms

- [CVE-2026-30944](https://insights.sbomify.com/CVE-2026-30944/): StudioCMS Affected by Privilege Escalation via Insecure API Token Generation (high 8.8)
- [CVE-2026-32101](https://insights.sbomify.com/CVE-2026-32101/): StudioCMS S3 Storage Manager Authorization Bypass via Missing `await` on Async Auth Check (high 7.6)
- [CVE-2026-30945](https://insights.sbomify.com/CVE-2026-30945/): StudioCMS: IDOR — Arbitrary API Token Revocation Leading to Denial of Service (high 7.1)
- [CVE-2026-32103](https://insights.sbomify.com/CVE-2026-32103/): StudioCMS: IDOR — Admin-to-Owner Account Takeover via Password Reset Link Generation (medium 6.8)
- [CVE-2026-24134](https://insights.sbomify.com/CVE-2026-24134/): StudioCMS has an Authorization Bypass Through User-Controlled Key (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-32638 and fix it if it is affected.

What it is: CVE-2026-32638 is a low-severity missing authorization vulnerability in withstudiocms studiocms, published on 18 Mar 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32638 exists.

Affected packages and fixed versions:
- studiocms (npm): affected all versions; fixed in 0.4.4
- studiocms (npm): affected all versions; fixed in 0.4.4

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-32638/ (Markdown: https://insights.sbomify.com/CVE-2026-32638/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-32638
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-32638
- OSV: https://osv.dev/vulnerability/CVE-2026-32638

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-32638/
Summaries are generated and may contain mistakes; the official description above is the record.