# CVE-2026-32103: StudioCMS: IDOR — Admin-to-Owner Account Takeover via Password Reset Link Generation

> Admin users can generate password reset tokens for any user, including the owner, leading to complete account takeover of the highest-privileged account.

- **Severity:** Medium 6.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/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:** 11 Mar 2026
- **Updated:** 12 Mar 2026
- **Also known as:** GHSA-h7vr-cg25-jf8c

## What is CVE-2026-32103?

CVE-2026-32103 is a medium-severity missing authorization vulnerability in withstudiocms studiocms, published on 11 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.3, the POST /studiocms_api/dashboard/create-reset-link endpoint allows any authenticated user with admin privileges to generate a password reset token for any other user, including the owner account. The handler verifies that the caller is an admin but does not enforce role hierarchy, nor does it validate that the target userId matches the caller's identity. Combined with the POST /studiocms_api/dashboard/reset-password endpoint, this allows a complete account takeover of the highest-privileged account in the system. This vulnerability is fixed in 0.4.3.

Weakness: CWE-640 (Weak Password Recovery Mechanism for Forgotten Password), CWE-639 (Authorization Bypass Through User-Controlled Key)

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

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.3 |
| `studiocms` | npm | All versions | 0.4.3 |

Products: Studiocms Studiocms.

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

Upgrade studiocms to 0.4.3 or later.

## Is CVE-2026-32103 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-32103 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-24134](https://insights.sbomify.com/CVE-2026-24134/): StudioCMS has an Authorization Bypass Through User-Controlled Key (medium 6.5)
- [CVE-2026-32104](https://insights.sbomify.com/CVE-2026-32104/): StudioCMS: IDOR in User Notification Preferences Allows Any Authenticated User to Modify Any User's Settings (medium 5.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-32103 is a medium-severity missing authorization vulnerability in withstudiocms studiocms, published on 11 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-32103 exists.

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

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-32103/ (Markdown: https://insights.sbomify.com/CVE-2026-32103/index.md)
```

## Sources

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

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