dbcve.org
Crafter CmsApplication · Craftercms

CVE-2022-40635

HIGH · 7.2 CVSS v3.1 Published 2022-09-13
Fix available
A fix is available. Upgrade to 3.1.23 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper Control of Dynamically-Managed Code Resources vulnerability in Crafter Studio of Crafter CMS allows authenticated developers to execute OS commands via Groovy Sandbox Bypass.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Crafter CMS contains a Groovy scripting sandbox that is intended to restrict code execution to safe operations. CVE-2022-40635 is a sandbox bypass vulnerability in Crafter Studio that allows authenticated developer accounts to circumvent these restrictions and execute arbitrary operating system commands through crafted Groovy scripts.

MitigationApply the vendor-released patch or upgrade to a fixed version of Crafter CMS. Review and restrict developer account permissions to the minimum required, and audit existing scripts for any malicious payloads that may have been injected during the window of exposure.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Crafter CmsApplication
Affected:>= 3.1.0, < 3.1.23

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Crafter CMS installed version
    Locate the version file or configuration in the Crafter CMS installation directory, typically found in the startup logs, version.properties file, or within Crafter Studio's admin console under 'About' or 'System Information'.
    Affected if The installed version is 3.1.0 through 3.1.22 (versions >= 3.1.0 and < 3.1.23).
  2. Verify access to Crafter Studio
    Confirm that Crafter Studio web application is accessible and running. This is typically accessible on the configured port (often 8080 or 8443) via HTTP/HTTPS.
    Affected if Crafter Studio is accessible without additional network segmentation or authentication at the perimeter.
  3. Confirm developer or admin accounts exist
    Check if there are any user accounts with Developer, Admin, or Script Writer roles in Crafter CMS. These roles typically have access to the Groovy scripting console within Crafter Studio.
    Affected if At least one account with Developer, Admin, or equivalent elevated privileges exists in the system.
  4. Verify Groovy scripting is enabled
    Within Crafter Studio, navigate to the Scripts console or site configuration to confirm the Groovy scripting module is available. Check site configuration files for script-related settings.
    Affected if The Groovy scripting feature is enabled and accessible to authenticated users in the CMS.

A user is affected if they are running Crafter CMS version 3.1.0 through 3.1.22 with Crafter Studio accessible and an account that has Developer-level or higher access to the Groovy scripting sandbox.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.1.23 or later
Fixed in 3.1.23
Interim mitigation

Apply the vendor-released patch or upgrade to a fixed version of Crafter CMS. Review and restrict developer account permissions to the minimum required, and audit existing scripts for any malicious payloads that may have been injected during the window of exposure.

Recommended fix High confidence

Crafter CMS 3.1.23

  1. Backup your Crafter CMS installation and database before upgrading
  2. Download Crafter CMS version 3.1.23 or later from the official distribution (docs.craftercms.org)
  3. Follow the official upgrade instructions for your deployment type
  4. Restart Crafter Studio services after applying the upgrade
  5. Verify the upgrade was successful by logging into Crafter Studio
  6. Confirm the Groovy sandbox is properly enforcing restrictions by testing code execution limits
Caveat Review the 3.1.23 release notes for any behavioral changes or deprecations that may affect your implementation

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Crafter Cms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,600.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-40635 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-40635 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data