CVE-2026-30944: StudioCMS is a server-side-rendered, Astro native, headless content management system

Q: How do I fix CVE-2026-30944?

studiocms: upgrade to 0.4.0. Exact commands for each OS are on this page.

Q: Is CVE-2026-30944 being exploited?

CVE-2026-30944 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2026-30944 affect?

CVE-2026-30944 affects studiocms. Severity is high (CVSS 8.8). 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 use

Q: How urgent is CVE-2026-30944?

Priority 48/100. High severity; Public exploit reference

This month

HIGH 8.8UPGRADE

CVE-2026-30944 is a high-severity flaw (CVSS 8.8) affecting studiocms. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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 v

Why this priority

High severity
Public exploit reference

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	Low
User interaction	None
EPSS exploit chance	0.6% (top 52%)
CISA exploited list	No
Weakness	CWE-639, CWE-863
Published	2026-03-10
Last modified	2026-06-17

Publisher (CNA): GitHub, Inc. · Vendor: studiocms

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2026-03-10 18:18 UTCPublished CVE record published
2026-06-17 10:33 UTCUpdated Record last modified

studiocms studiocms UPGRADE

Affected: < 0.4.0

Fixed in: 0.4.0

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy studiocms || rpm -q studiocms || studiocms --version

2. UPGRADE to 0.4.0 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade studiocms

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade studiocms

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2026-30944?

studiocms: upgrade to 0.4.0. Exact commands for each OS are on this page.

Is CVE-2026-30944 being exploited?

CVE-2026-30944 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2026-30944 affect?

CVE-2026-30944 affects studiocms. Severity is high (CVSS 8.8). 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 use

How urgent is CVE-2026-30944?

Priority 48/100. High severity; Public exploit reference

Related CVEs

CVE-2026-32638 LOW 2.7 UPGRADE StudioCMS is a server-side-rendered, Astro native, headless content management system
CVE-2026-30945 HIGH 7.1 UPGRADE StudioCMS is a server-side-rendered, Astro native, headless content management system
CVE-2026-24134 MEDIUM 6.5 UPGRADE StudioCMS is a server-side-rendered, Astro native, headless content management system

References

← Back to latest CVEs