dbcve.org
Crafter CmsApplication · Craftercms

CVE-2022-40634

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 FreeMarker SSTI.

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 · moderate confidence

Crafter Studio in Crafter CMS contains a Server-Side Template Injection (SSTI) vulnerability in the FreeMarker templating engine. Authenticated developers with studio access can inject malicious FreeMarker template directives that bypass sandboxing and execute arbitrary operating system commands on the host server.

MitigationApply the vendor patch for CVE-2022-40634 to Crafter CMS. Additionally, restrict FreeMarker template execution permissions for developer accounts, implement strict input validation for template contexts, and review the principle of least privilege for Crafter Studio users.

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 installed Crafter CMS version
    Check the version file or startup logs. Common locations: $CRAFTER_HOME/craftercms-version.txt, or look in catalina.out/crafter.log for version strings during startup.
    Affected if Installed version is 3.1.0 or higher but lower than 3.1.23
  2. Verify Crafter Studio web interface is accessible
    Confirm the Studio application is deployed and reachable. Typically at port 8080 or 8081 under /studio or the root path. Check server.xml for deployed web applications.
    Affected if Studio interface responds to HTTP requests, indicating the vulnerable component is exposed
  3. Confirm FreeMarker templating is in use
    Examine the Crafter configuration for site content using FreeMarker templates. Look for .ftl files in /data/repos/sites/{sitename}/templates or check if FreeMarker is the configured rendering engine in site configuration.
    Affected if FreeMarker templates (.ftl) exist in the repository or are configured as the default templating engine
  4. Check for developer or author accounts with Studio access
    Review user accounts in Studio's user management. Users with Developer or Admin roles in Studio can create and edit templates. Query the database or check /crafter/studio/data/users or the internal database.
    Affected if Any authenticated user exists with permission to access Studio and create/edit templates

The environment is affected if Crafter CMS version is between 3.1.0 and 3.1.22 inclusive, Crafter Studio is accessible, FreeMarker templates are used, and at least one user has developer-level studio access to potentially exploit the SSTI vulnerability.

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 patch for CVE-2022-40634 to Crafter CMS. Additionally, restrict FreeMarker template execution permissions for developer accounts, implement strict input validation for template contexts, and review the principle of least privilege for Crafter Studio users.

Recommended fix High confidence

3.1.23 or later

  1. 1. Backup your current Crafter CMS installation and database before proceeding
  2. 2. Download Crafter CMS version 3.1.23 or later from the official Crafter CMS downloads page (https://craftercms.org/downloads/)
  3. 3. Stop the Crafter CMS services running on your server
  4. 4. Follow the official upgrade instructions for your deployment type (single server or cluster)
  5. 5. Verify the upgrade was successful by logging into Crafter Studio
  6. 6. Test that FreeMarker templates function normally after the upgrade
  7. 7. Monitor logs for any errors related to the upgrade
Caveat Review release notes for 3.1.23 to check for any configuration or feature changes 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
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-40634 — 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-40634 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