Vulnerability Database · Maven · Package report

org.craftercms:crafter-studio: vulnerability history, versions and safety

org.craftercms:crafter-studio is a package in the Maven ecosystem. Vulert records 10 vulnerabilities for it across 115 releases, from Dec 2018 to Jun 2025. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
10 vulnerabilities recorded C1 H8 M1
i
1 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

Vulert verdict on org.craftercms:crafter-studio 4.3.1 i

Updated on 23 Oct 2026

Careful: 4.3.1 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Maintaining
  • Popularity Little adoption
  • Community Not enough data

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 4.3.1 — affected i
  • Vulnerabilities on record 10 over 6 years · 0 in the last year i
  • Latest disclosure 19 Jun 2025 i
  • Highest CVSS 9.8 i
  • With no published fix 1 i
  • Last release 18 months ago i
  • Licence GPL-3.0 i

Version list, release dates, licence and dependants published by Maven Central, 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 org.craftercms:crafter-studio, 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
4.3.1 02 Apr 2025 H1 GPL-3.0 No Details →
4.3.0 21 Feb 2025 H1 GPL-3.0 No Details →
4.2.2 16 Jan 2025 H1 GPL-3.0 Yes Details →
4.2.1 15 Jan 2025 H1 GPL-3.0 Yes Details →
4.1.9 27 Nov 2024 H1 GPL-3.0 Yes Details →
4.1.8 13 Sep 2024 H1 — Yes Details →
4.1.7 12 Sep 2024 H1 GPL-3.0 Yes Details →
4.1.6 19 Aug 2024 H1 GPL-3.0 Yes Details →
4.1.5 30 May 2024 H1 GPL-3.0 Yes Details →
3.1.31E 19 Sep 2023 H1 GPL-3.0 No Details →
3.1.31 19 Sep 2023 H1 GPL-3.0 No Details →
4.0.6 04 Jul 2023 H1 GPL-3.0 Yes Details →
4.0.5 07 Jun 2023 H1 GPL-3.0 Yes Details →
4.0.4 02 Jun 2023 H1 GPL-3.0 Yes Details →
3.1.30E 04 May 2023 H1 GPL-3.0 No Details →
3.1.30 04 May 2023 H1 GPL-3.0 No Details →
3.1.29E 24 Jan 2023 H1 GPL-3.0 No Details →
3.1.29 24 Jan 2023 H1 GPL-3.0 No Details →
3.1.28E 21 Dec 2022 H1 GPL-3.0 No Details →
3.1.28 21 Dec 2022 H1 GPL-3.0 No Details →
4.0.2 25 Oct 2022 H1 GPL-3.0 Yes Details →
3.1.27E 01 Oct 2022 H1 GPL-3.0 No Details →
3.1.27 01 Oct 2022 H1 GPL-3.0 No Details →
4.0.1 16 Sep 2022 H1 GPL-3.0 Yes Details →
3.1.26E 09 Sep 2022 H1 GPL-3.0 No Details →
3.1.26 09 Sep 2022 H1 GPL-3.0 No Details →
3.1.25E 29 Aug 2022 H1 GPL-3.0 No Details →
3.1.25 29 Aug 2022 H1 GPL-3.0 No Details →
3.1.24E 08 Jul 2022 H1 GPL-3.0 No Details →
3.1.24 08 Jul 2022 H1 GPL-3.0 No Details →
3.1.23E 27 Apr 2022 H2 GPL-3.0 No Details →
3.1.23 27 Apr 2022 H1 GPL-3.0 No Details →
4.0.0-rc2E 08 Mar 2022 H1 GPL-3.0 No Details →
4.0.0-rc2 08 Mar 2022 H1 — No Details →
3.1.22E 23 Feb 2022 H1 GPL-3.0 Yes Details →
3.1.22 23 Feb 2022 H1 GPL-3.0 Yes Details →
3.1.21E 07 Feb 2022 H1 GPL-3.0 Yes Details →
3.1.21 07 Feb 2022 H1 GPL-3.0 Yes Details →
3.1.20E 01 Feb 2022 H1 GPL-3.0 Yes Details →
3.1.20 01 Feb 2022 H1 GPL-3.0 Yes Details →
3.1.19E 31 Jan 2022 H1 GPL-3.0 Yes Details →
3.1.19 31 Jan 2022 H1 GPL-3.0 Yes Details →
3.1.18E 19 Jan 2022 H1 GPL-3.0 Yes Details →
3.1.18 19 Jan 2022 H1 GPL-3.0 Yes Details →
4.0.0-rc1E 07 Jan 2022 H1 GPL-3.0 No Details →
4.0.0-rc1 07 Jan 2022 H1 GPL-3.0 No Details →
3.1.17.7E 05 Jan 2022 H2 GPL-3.0 Yes Details →
3.1.17.7 05 Jan 2022 H2 GPL-3.0 Yes Details →
3.1.17.6E 19 Dec 2021 H2 GPL-3.0 Yes Details →
3.1.17.6 19 Dec 2021 H2 GPL-3.0 Yes Details →
3.1.17.5E 18 Dec 2021 H2 GPL-3.0 Yes Details →
3.1.17.5 18 Dec 2021 H2 GPL-3.0 Yes Details →
3.1.17.4E 17 Dec 2021 H2 GPL-3.0 Yes Details →
3.1.17.4 16 Dec 2021 H2 GPL-3.0 Yes Details →
3.1.17 09 Aug 2021 H2 GPL-3.0 Yes Details →
3.1.17E 09 Aug 2021 H2 GPL-3.0 Yes Details →
3.1.16 13 Jul 2021 H2 GPL-3.0 Yes Details →
3.1.16E 13 Jul 2021 H2 GPL-3.0 Yes Details →
3.1.15E 24 Jun 2021 H2 GPL-3.0 Yes Details →
3.1.15 24 Jun 2021 H2 GPL-3.0 Yes Details →
3.1.14 03 May 2021 H2 GPL-3.0 Yes Details →
3.1.14E 03 May 2021 H2 GPL-3.0 Yes Details →
3.1.13 16 Feb 2021 H2 GPL-3.0 Yes Details →
3.1.13E 16 Feb 2021 H2 GPL-3.0 Yes Details →
3.1.12 08 Jan 2021 H2 GPL-3.0 Yes Details →
3.1.12E 08 Jan 2021 H2 GPL-3.0 Yes Details →
3.1.11E 25 Nov 2020 H2 GPL-3.0 Yes Details →
3.1.11 25 Nov 2020 H2 GPL-3.0 Yes Details →
3.1.10E 09 Oct 2020 H2 GPL-3.0 Yes Details →
3.1.10 09 Oct 2020 H2 GPL-3.0 Yes Details →
3.1.9E 21 Aug 2020 H2 GPL-3.0 Yes Details →
3.1.9 20 Aug 2020 H2 GPL-3.0 Yes Details →
3.1.8E 01 Jul 2020 H2 GPL-3.0 Yes Details →
3.1.8 01 Jul 2020 H2 GPL-3.0 Yes Details →
3.0.27 09 Jun 2020 H1 GPL-3.0 No Details →
3.1.7 03 Jun 2020 H2 GPL-3.0 Yes Details →
3.1.7E 03 Jun 2020 H2 GPL-3.0 Yes Details →
3.1.6E 22 Apr 2020 H2 GPL-3.0 Yes Details →
3.1.6 22 Apr 2020 H2 GPL-3.0 Yes Details →
3.1.5E 22 Feb 2020 H2 GPL-3.0 Yes Details →
3.1.5 22 Feb 2020 H2 GPL-3.0 Yes Details →
3.1.4E 11 Dec 2019 H2 GPL-3.0 Yes Details →
3.1.4t 09 Dec 2019 H2 GPL-3.0 Yes Details →
3.1.4 26 Nov 2019 H2 GPL-3.0 Yes Details →
3.1.2 07 Nov 2019 H2 GPL-3.0 Yes Details →
3.0.26 07 Nov 2019 H2 GPL-3.0 Yes Details →
3.0.22 07 Nov 2019 H2 GPL-3.0 Yes Details →
3.0.21 07 Nov 2019 H2 GPL-3.0 Yes Details →
3.0.25 07 Nov 2019 H2 GPL-3.0 Yes Details →
3.1.3 07 Nov 2019 H2 GPL-3.0 Yes Details →
3.0.24 07 Nov 2019 H2 GPL-3.0 Yes Details →
3.1.1 07 Nov 2019 H2 GPL-3.0 Yes Details →
3.0.23 07 Nov 2019 H2 GPL-3.0 Yes Details →
3.1.0 07 Nov 2019 H2 GPL-3.0 Yes Details →
3.0.9 19 Jul 2019 H3 GPL-3.0 No Details →
3.0.8 19 Jul 2019 H3 GPL-3.0 No Details →
3.0.7 19 Jul 2019 H3 GPL-3.0 No Details →
3.0.6 19 Jul 2019 H3 GPL-3.0 No Details →
3.0.5 19 Jul 2019 H3 GPL-3.0 No Details →
3.0.4 19 Jul 2019 H3 GPL-3.0 No Details →
3.0.3 19 Jul 2019 H3 — No Details →
3.0.20 19 Jul 2019 H2 — Yes Details →
3.0.2 19 Jul 2019 H3 — No Details →
3.0.19 19 Jul 2019 H2 — Yes Details →
3.0.18 19 Jul 2019 H3 — No Details →
3.0.17 19 Jul 2019 H3 — No Details →
3.0.16 19 Jul 2019 H3 — No Details →
3.0.15 19 Jul 2019 H3 — No Details →
3.0.14 19 Jul 2019 H3 — No Details →
3.0.13 19 Jul 2019 H3 — No Details →
3.0.12 19 Jul 2019 H3 — No Details →
3.0.11 19 Jul 2019 H3 — No Details →
3.0.10 19 Jul 2019 H3 — No Details →
3.0.1 19 Jul 2019 C1 H5 M1 — No Details →
3.0.0 19 Jul 2019 C1 H5 M1 — No Details →

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

02 Disclosure history

How often vulnerabilities are recorded

  • 2018 1
  • 2022 8
  • 2025 1

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

03 Vulnerabilities

Recorded vulnerabilities for org.craftercms:crafter-studio

The 5 most severe of 10 vulnerabilities recorded for this package

Search all 10 in the database →

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 org.craftercms:crafter-studio

Is org.craftercms:crafter-studio safe to use?

Vulert records 10 vulnerabilities for org.craftercms:crafter-studio in Maven: 1 critical, 8 high, 1 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is org.craftercms:crafter-studio's Vulert package health score?

Vulert scores org.craftercms:crafter-studio 60/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). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of org.craftercms:crafter-studio affected?

Yes. 4.3.1, the version you would install today, has 1 known vulnerability, and 1 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of org.craftercms:crafter-studio should I use?

4.3.1 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does org.craftercms:crafter-studio have?

10 vulnerabilities are recorded for org.craftercms:crafter-studio in the Maven ecosystem: 1 critical, 8 high, 1 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.craftercms:crafter-studio vulnerabilities disclosed?

0 vulnerabilities were recorded for org.craftercms:crafter-studio in the last 12 months, and the oldest entry in this database dates to 19 Dec 2018. 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 org.craftercms:crafter-studio 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 org.craftercms:crafter-studio for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the org.craftercms:crafter-studio version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.