Vulnerability Database · npm · studiocms · Version
studiocms 0.2.0
0.2.0 is affected by 6 vulnerabilities.
The vulnerabilities that cover this exact version are listed below with the fixed version to move to.
Critical 0 High 2 Medium 3 Low 1 Unrated 0
-
Released 27 Jan 2026
Licence MIT
Also known from other sources 6
Newer releases 40
Database updated 23/Oct/2026
Release and licence data published by the npm registry. Licence information is not legal advice.
Concerned about your application's security?
Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.
01 Vulnerabilities affecting this version
studiocms 0.2.0 vulnerabilities
6 vulnerabilities cover studiocms 0.2.0. Open the full list in the database.
| Vulnerability | Severity | Fixed version | Disclosed |
|---|---|---|---|
| CVE-2026-30944: StudioCMS Privilege Escalation via Insecure API Token Generation | 8.8 high | 0.4.0 | 10 Mar 2026 |
| CVE-2026-30945: StudioCMS Arbitrary API Token Revocation Vulnerability | 7.1 high | 0.4.0 | 11 Mar 2026 |
| CVE-2026-32103: StudioCMS Admin-to-Owner Account Takeover via Password Reset Link Generation | 6.8 medium | 0.4.3 | 12 Mar 2026 |
| CVE-2026-32104: StudioCMS IDOR Vulnerability Allows Unauthorized Modification of User Notification Preferences | 5.4 medium | 0.4.3 | 12 Mar 2026 |
| CVE-2026-32106: StudioCMS REST API Allows Unauthorized Creation of Peer Admin Accounts | 4.7 medium | 0.4.3 | 12 Mar 2026 |
| CVE-2026-32638: StudioCMS REST API Allows Admins to Access Owner Account Records | 2.7 low | 0.4.4 | 16 Mar 2026 |
Looking for another version, or everything Vulert holds for studiocms?
Questions
About studiocms 0.2.0
Is studiocms 0.2.0 vulnerable?
Yes. 6 vulnerabilities in the Vulert database cover studiocms 0.2.0: 0 critical, 2 high, 3 medium and 1 low. Each entry above names the fixed version to move to.
Is 0.2.0 the latest release of studiocms?
No. 0.2.0 was published 27 Jan 2026, and newer releases exist. Newer is not automatically safer — the version table on the package page shows what each release carries.
How do I monitor studiocms for upcoming vulnerabilities?
Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the studiocms version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.