CVE intelligence and bounded remediation
CVE-2026-30944 — StudioCMS is a server-side-rendered, Astro native, headless content management system
StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.0, the /studiocms_api/dashboard/api-tokens endpoint allows any authenticated user (at least Editor) to generate API tokens for any other user, including owner and admin accounts. The endpoint fails to validate whether the requesting user is authorized to create tokens on behalf of the target user ID, resulting in a full privilege escalation. This vulnerability is fixed in 0.4.0.
- Severity
- High
- CVSS
- 8.8 (3.1)
- Published
- 2026-03-10
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-639, CWE-863
Affected products
- studiocms / studiocms
Matched remediation archetype
Authorization bypass, IDOR, and cross-tenant access
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Map object and action authorization checks across API, UI, batch, import/export, and background-job paths.
- Identify tenant, ownership, role, and policy boundaries for affected resources and administrative operations.
- Use synthetic fixtures to compare intended access matrices without accessing another user's real data.
Remediate safely
- Enforce server-side authorization at each resource access and state transition using the authenticated principal and trusted tenant context.
- Scope data queries by tenant and ownership; treat client-supplied identifiers, roles, and policy claims as untrusted.
- Add deny-by-default policy tests for horizontal and vertical access across every affected transport.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.