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

published 2026-03-11 7 mo ago modified 2026-06-17 4 mo ago also GHSA-h7vr-cg25-jf8c , EUVD-2026-11371

cvss: 6.8; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.4%; EPSS 0.4% chance of exploitation in 30 days, percentile 33%
public exploits: 0; none known

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.

Patch / fix

fixed in 2

npm studiocms 0.4.3
studiocms studiocms 0.4.3

CISA SSVC

Exploitation: Proof of concept is public
Automatable: no
Technical impact: partial
Assessed: 7 mo ago (2026-03-12)

Exploit prediction

0.39% chance of exploitation in the next 30 days, higher than 33% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

github.com https://github.com/withstudiocms/studiocms/security/advisories/GHSA-h7vr-cg25-jf8c referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
CNA	3.1	6.8	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:N
NVD	3.1	7.2	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
GitHub	3.1	6.8	CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:N/I:H/A:N

Affected packages

ecosystem	package	affected	fixed in
npm	studiocms	<0.4.3	0.4.3

Affected products

withstudiocms studiocms

Classification

Weakness

CWE-639 Authorization Bypass Through User-Controlled Key
CWE-640 Weak Password Recovery Mechanism for Forgotten Password

References

github.com /withstudiocms/studiocms/security/advisories/GHSA-h7vr-cg25-jf8c
web, exploit, vendor-advisory
nvd.nist.gov /vuln/detail/CVE-2026-32103
advisory
github.com /withstudiocms/studiocms
package

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary