Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.8amended

StudioCMS: IDOR — Admin-to-Owner Account Takeover via Password Reset Link Generation

CVE-2026-32103GHSA-h7vr-cg25-jf8c

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (studiocms 0.4.3), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
6.8 · CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:N
EPSS
  • CVE-2026-32103: 0.36% estimated exploitation activity in the next 30 days; percentile 30.38 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The POST /studiocmsapi/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 /studiocmsapi/dashboard/reset-password endpoint, this allows a complete account takeover of the highest-privileged account in the system. Details Vulnerable Code File: packages/studiocms/frontend/pages/studiocmsapi/dashboard/create-reset-link.ts Version: studiocms@0.3.0 Analysis Unlike the API token endpoints (which only require isEditor), this handler correctly gates access at the isAdmin level [1]. However, two critical authorization checks are still missing: 1. No caller identity validation [2][3]: The userId from the JSON payload is never compared against the authenticated caller's session identity.…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-h7vr-cg25-jf8c

  2. Revision 1 · created ·

    Published from osv record GHSA-h7vr-cg25-jf8c

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-32103

Advisory: StudioCMS: IDOR — Admin-to-Owner Account Takeover via Password Reset Link Generation
IDs: CVE-2026-32103, GHSA-h7vr-cg25-jf8c
Record: https://patchnext.com/advisories/cve-2026-32103 (revision 2, source checked 26 Oct 2026, 12:43 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.8)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: studiocms 0.4.3. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm studiocms: affected <= 0.4.2; fixed in 0.4.3

## Suggested inspection (read-only)
- `npm ls studiocms --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on studiocms.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-h7vr-cg25-jf8c (OSV record GHSA-h7vr-cg25-jf8c lists affected ranges: npm studiocms >=0 <0.4.3 (fixed))
- Verified: https://github.com/advisories/GHSA-h7vr-cg25-jf8c (GitHub-reviewed advisory GHSA-h7vr-cg25-jf8c lists affected ranges: npm studiocms >=0 <=0.4.2)

Commands are suggestions: review each one before running it.

Loading voting…