org.craftercms:crafter-studio vulnerabilities
Crafter Content Authoring Application
- Registry
- Maven
- Latest
- 4.3.1
10 known advisories
The latest version, 4.3.1, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.craftercms:crafter-studio -DdepVersion=4.3.1 -DforceVersion=trueIs your project on an affected org.craftercms:crafter-studio?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.craftercms:crafter-studio
Crafter Studio Groovy Sandbox Bypass
- Affected
- >=4.0.0 <4.3.0
- Fixed in
- 4.3.0
CrafterCMS Crafter Studio Improperly Controls Dynamically-Managed Code Resources
- Affected
- >=3.1.0 <3.1.23
- Fixed in
- 3.1.23
Crafter CMS Crafter Studio vulnerable to Improper Control of Dynamically-Managed Code Resources
- Affected
- >=3.1.0 <3.1.18
- Fixed in
- 3.1.18
Cross-site scripting in Crafter CMS Crafter Studio
- Affected
- <3.0.2
- Fixed in
- 3.0.2
Path Traversal in Crafter CMS Crafter Studio
- Affected
- <3.0.2
- Fixed in
- 3.0.2
XML Injection in Crafter CMS Crafter Studio 3.0.1
- Affected
- <3.0.2
- Fixed in
- 3.0.2
Path Traversal in Crafter CMS Crafter Studio
- Affected
- <3.0.2
- Fixed in
- 3.0.2
Improper Control of Dynamically-Managed Code Resources in Crafter CMS Crafter Studio
- Affected
- >=3.0 <3.0.27 · >=3.1 <3.1.7
- Fixed in
- 3.0.27, 3.1.7
Improper Control of Dynamically-Managed Code Resources in Crafter CMS Crafter Studio
- Affected
- >=3.0 <3.0.27 · >=3.1 <3.1.7
- Fixed in
- 3.0.27, 3.1.7
OS Command Injection in craftercms:crafter-studio
- Affected
- <=3.0.18
- Fixed in
- No fix released
Is your org.craftercms:crafter-studio version vulnerable?
- org.craftercms:crafter-studio 4.3No known advisories in 4.3.1
- org.craftercms:crafter-studio 4.21 advisory in 4.2.2
- org.craftercms:crafter-studio 4.11 advisory in 4.1.9
- org.craftercms:crafter-studio 4.01 advisory in 4.0.6
- org.craftercms:crafter-studio 3.1No known advisories in 3.1.31
- org.craftercms:crafter-studio 3.0No known advisories in 3.0.27
Which of your client projects still run an old org.craftercms:crafter-studio?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.