Signal is active with 2 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD description
StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.0, the DELETE /studiocms_api/dashboard/api-tokens endpoint allows any authenticated user with editor privileges or above to revoke API tokens belonging to any other user, including admin and owner accounts. The handler accepts tokenID and userID directly from the request payload without verifying token ownership, caller identity, or role hierarchy. This enables targeted denial of service against critical integrations and automations. This vulnerability is fixed in 0.4.0.
Priority
LOW
Exploitation
NONE
PoC
YES
Patch
AVAILABLE
Momentum
NONE
If you run products in this scope, you should treat this CVE as relevant to your environment.
CVE-2026-30945 StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.0, the DELETE /studiocms_api/dashboard/api-tokens endpoint allows … https://www.cve.org/CVERecord?id=CVE-2026-30945
Post summary
The text references CVE‑2026‑30945 and notes a vulnerability in a DELETE endpoint, but provides limited detail and no supporting PoC, exploit, or patch information.
🚨*CVE* CVE-2026-30945 StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.0, the DELETE /studiocms_api/dashboard/api-tokens endpoint allows … https://www.cve.org/CVERecord?id=CVE-2026-30945 ----- Traducción: CVE-2026-30945 Stu… http://infoflow.cloud`
Post summary
A CVE-2026-30945 vulnerability in StudioCMS pre‑0.4.0 affecting the DELETE /studiocms_api/dashboard/api-tokens endpoint is mentioned, providing basic technical details but no PoC, exploit code, or patch information.
1 of 1 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| App | studiocms | studiocms | - | - | - |