VulertSecurity VulertSecurity

Vulnerability Database · npm · Package report

studiocms: vulnerability history, versions and safety

studiocms is a package in the npm ecosystem. Vulert records 7 vulnerabilities for it across 35 releases, from Jan 2026 to Mar 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
7 vulnerabilities recorded H2 M4 L1
i
0 with no fix published

Every vulnerability has a patched version to move to.

i
7 in the last 12 months

Most recent disclosure 16 Mar 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all studiocms vulnerabilities

Vulert verdict on studiocms 0.7.0 i

Updated on 23 Oct 2026

Good news: 0.7.0, the version you would install today, has no known vulnerabilities. Older releases do — the table below lists all 7.

Package health score 62/100
  • Security Some issues to review
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

What to do: Stay on 0.7.0 or newer. This can change: a vulnerability disclosed tomorrow can affect 0.7.0 too — Vulert watches the package and alerts you if that happens. Monitor it with Vulert →

  • Current release 0.7.0 — unaffected i
  • Vulnerabilities on record 7 over 1 year · 7 in the last year i
  • Latest disclosure 16 Mar 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 0 i
  • Stars 840 i
  • Last release this month i
  • Licence MIT i

Version list, release dates, licence and dependants published by the npm registry, refreshed 22 Oct 2026. 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 Versions

Which versions are affected

Every version Vulert tracks for studiocms, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
0.7.0 19 Oct 2026 none MIT — Details →
0.6.1 01 Oct 2026 none MIT — Details →
0.6.0 26 Sep 2026 none MIT — Details →
0.5.0 24 Sep 2026 none MIT — Details →
0.4.4 14 Mar 2026 none MIT — Details →
0.4.3 11 Mar 2026 L1 MIT Yes Details →
0.4.2 10 Mar 2026 M3 L1 MIT Yes Details →
0.4.1 10 Mar 2026 M3 L1 MIT Yes Details →
0.4.0 10 Mar 2026 M3 L1 MIT Yes Details →
0.3.0 07 Feb 2026 H2 M3 L1 MIT Yes Details →
0.2.0 27 Jan 2026 H2 M3 L1 MIT Yes Details →
0.1.1 16 Jan 2026 H2 M4 L1 MIT Yes Details →
0.1.0 15 Jan 2026 H2 M4 L1 MIT Yes Details →
0.1.0-beta.31 17 Dec 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.30 11 Nov 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.29 09 Nov 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.28 29 Oct 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.27 27 Sep 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.26 05 Sep 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.25 25 Aug 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.24 11 Aug 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.23 02 Aug 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.22 31 Jul 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.21 23 Jul 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.20 22 Jul 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.19 20 Jul 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.18 11 May 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.17 26 Apr 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.16 20 Apr 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.15 09 Apr 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.14 31 Mar 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.13 26 Mar 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.12 14 Mar 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.11 05 Mar 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.10 04 Mar 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.9 28 Feb 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.8 28 Feb 2025 H2 M4 L1 MIT Yes Details →
0.1.0-beta.7 24 Sep 2024 H2 M4 L1 MIT Yes Details →
0.1.0-beta.6 14 Sep 2024 H2 M4 L1 MIT Yes Details →
0.1.0-beta.5 05 Sep 2024 H2 M4 L1 MIT Yes Details →

All 40 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2026 7

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 7 of the 7 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for studiocms

The 5 most severe of 7 vulnerabilities recorded for this package

Search all 7 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-24134: StudioCMS Authorization Bypass Vulnerability in Content Management 6.5 medium 0.2.0 27 Jan 2026
CVE-2026-32104: StudioCMS IDOR Vulnerability Allows Unauthorized Modification of User Notification Preferences 5.4 medium 0.4.3 12 Mar 2026

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About studiocms

Is studiocms safe to use?

Vulert records 7 vulnerabilities for studiocms in npm: 0 critical, 2 high, 4 medium and 1 low. Every one of them has a published fix, so the practical answer is to run a supported release and keep it patched.

What is studiocms's Vulert package health score?

Vulert scores studiocms 62/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15).

Is the latest version of studiocms affected?

No. 0.7.0, the version you would install today, has no vulnerabilities on record against it. Earlier releases do — the version table above lists each release with what affects it.

How many vulnerabilities does studiocms have?

7 vulnerabilities are recorded for studiocms in the npm ecosystem: 0 critical, 2 high, 4 medium and 1 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new studiocms vulnerabilities disclosed?

7 vulnerabilities were recorded for studiocms in the last 12 months, and the oldest entry in this database dates to 27 Jan 2026. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of studiocms are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

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.