# StudioCMS has Privilege Escalation via Insecure API Token Generation

Advisory record · `GHSA-667w-mmh7-mrr4`

- **Identifiers:** `GHSA-667w-mmh7-mrr4` · `CVE-2026-30944`
- **State:** Confirmed
- **Severity:** CVSS 8.8 High
- **Critical:** No
- **Weakness (CWE):** [CWE-639](https://cwe.mitre.org/data/definitions/639.html) · [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 10 Mar 2026
- **Updated:** 10 Mar 2026
- **Reviewed by a person:** No

Published by the GitHub Advisory Database at 10 Mar 2026, 18:16 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

## Affected packages

- `studiocms` (npm): affected `<0.4.0`; fixed in `0.4.0`

## Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

## Severity and exploitation

- 8.8 High, CVSS 3.1: `CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0064, the 51st percentile, on 19 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

This record came from the full history of the GitHub Advisory Database, published 10 Mar 2026. New records show when each source confirmed them.

## Sources

- [GitHub Advisory Database: GHSA-667w-mmh7-mrr4](https://github.com/advisories/GHSA-667w-mmh7-mrr4)
- [OSV: GHSA-667w-mmh7-mrr4](https://osv.dev/vulnerability/GHSA-667w-mmh7-mrr4)
- <https://github.com/withstudiocms/studiocms/security/advisories/GHSA-667w-mmh7-mrr4>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-30944>
- <https://github.com/withstudiocms/studiocms/commit/9eec9c3b45523b635cfe16d55aa55afabacbebe3>
- <https://github.com/withstudiocms/studiocms/commit/f4a209fc090c90195e2419fff47b48a46eab7441>
- <https://github.com/withstudiocms/studiocms>
- <https://github.com/withstudiocms/studiocms/releases/tag/studiocms%400.4.0>
- <https://github.com/withstudiocms/studiocms/releases/tag/studiocms@0.4.0>

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-667w-mmh7-mrr4>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-667w-mmh7-mrr4/>. Everything for agents: <https://agentprime.io/llms.txt>.
