How severe is CVE-2026-30945?

CVE-2026-30945 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability high.

Is CVE-2026-30945 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (36th percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-30945?

CVE-2026-30945 affects Studiocms. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-30945?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2026-30945 have an EU (EUVD) identifier?

Yes. CVE-2026-30945 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-10557.

When was CVE-2026-30945 published?

CVE-2026-30945 was published on 2026-03-10 and last updated on 2026-06-17.

CVE-2026-30945

CVE-2026-30945 is a high-severity vulnerability in Studiocms with a CVSS 3.x base score of 7.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-639.

Key facts

Severity: High (CVSS 3.x base score 7.1)
EPSS exploit prediction: 0% (36th percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2026-10557
Weakness: CWE-639
Affected product: Studiocms
Published: 2026-03-10
Last modified: 2026-06-17

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.

Frequently asked questions

What is 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 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.
How severe is CVE-2026-30945?: CVE-2026-30945 has a CVSS 3.x base score of 7.1, rated high severity. It is exploitable over network with low attack complexity, requires low privileges and no user interaction. Impact on confidentiality is none, integrity low, and availability high.
Is CVE-2026-30945 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (36th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-30945?: CVE-2026-30945 affects Studiocms. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-30945?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2026-30945 have an EU (EUVD) identifier?: Yes. CVE-2026-30945 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2026-10557.
When was CVE-2026-30945 published?: CVE-2026-30945 was published on 2026-03-10 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:studiocms:studiocms:*:*:*:*:*:*:*:*

More vulnerabilities in Studiocms

CVE-2026-30944 — High (CVSS 8.8): StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.0, the…
CVE-2026-32101 — High (CVSS 7.6): StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.3.1, the S3 storage…
CVE-2026-32103 — Medium (CVSS 6.8): StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.3, the POST…
CVE-2026-24134 — Medium (CVSS 6.5): StudioCMS is a server-side-rendered, Astro native, headless content management system. Versions prior to 0.2.0 contain…
CVE-2026-32104 — Medium (CVSS 5.4): StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.3, the…
CVE-2026-32106 — Medium (CVSS 4.7): StudioCMS is a server-side-rendered, Astro native, headless content management system. Prior to 0.4.3, the REST API…

All CVEs affecting Studiocms →

Other CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities

CVE-2025-40805 — Critical (CVSS 10.0): Affected devices do not properly enforce user authentication on specific API endpoints. This could facilitate an…
CVE-2024-45032 — Critical (CVSS 10.0): A vulnerability has been identified in Industrial Edge Management Pro (All versions < V1.9.5), Industrial Edge…
CVE-2026-34037 — Critical (CVSS 9.9): Coolify is an open-source and self-hostable tool for managing servers, applications, and databases. Prior to…
CVE-2026-52782 — Critical (CVSS 9.9): OpenProject is open-source, web-based project management software. Prior to 17.3.3 and 17.4.1, there is an IDOR through…
CVE-2026-45552 — Critical (CVSS 9.9): Roxy-WI is a web interface for managing Haproxy, Nginx, Apache and Keepalived servers. In versions 8.2.6.4 and prior,…
CVE-2026-29200 — Critical (CVSS 9.9): A critical IDOR vulnerability has been discovered in Comet Backup affecting all versions from 20.11.0 to 26.1.1 and…

Browse all CWE-639 (Authorization Bypass Through User-Controlled Key (IDOR)) vulnerabilities →