dbcve.org
Crafter CmsApplication · Craftercms

CVE-2021-23267

HIGH · 8.8 CVSS v3.1 Published 2022-05-16
Fix available
A fix is available. Upgrade to 3.1.18 or later.
See remediation →
94/100
Remediation priority · Urgent
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 static methods.

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 Crafter Studio contains a code injection vulnerability where authenticated developer accounts can execute arbitrary operating system commands by leveraging FreeMarker template static methods. The vulnerability allows improper control of dynamically-managed code resources (the FreeMarker templating engine), enabling attackers with developer-level access to escape the sandbox and execute OS-level commands.

MitigationRestrict or disable OS command execution capabilities in FreeMarker templates, apply principle of least privilege to developer accounts, and upgrade to the patched Crafter CMS version.

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, < 3.1.18

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 if Crafter CMS is installed
    Check for Crafter CMS installation directories (common paths: /opt/crafter, /crafter, or C:\crafter on Windows). Look for the crafter.sh/crafter.bat startup scripts or the Crafter Studio web application (studio.war) in the installation.
    Affected if Crafter CMS is found on the system
  2. Determine the installed Crafter CMS version
    Check the version file typically located at {install_dir}/crafter.sh/version.txt or access Crafter Studio's About page (typically /studio/static-assets/app/about.html or via the admin console). The version format is typically 3.x.x.
    Affected if Version is 3.1.x and is lower than 3.1.18 (e.g., 3.1.0 through 3.1.17)
  3. Verify developer-level accounts exist
    Log into Crafter Studio admin console and navigate to Users/Groups administration, or inspect the database tables (crafter.mysql or Oracle) for user records with role type 'developer' or 'admin'. Check for any enabled user accounts with elevated permissions.
    Affected if At least one user account with developer or admin privileges is active in the system
  4. Confirm FreeMarker template processing is enabled
    Check Crafter Studio configuration files (especially main-site-config.xml or the FreeMarker configuration in {install_dir}/data/repos/sites/{sitename}/config/studio/configuration) for template processing settings. Verify that FreeMarker template engine is active by accessing the Sites > {site} > Tools > Templates section in Crafter Studio.
    Affected if FreeMarker templating is enabled and users can access template editing/creation features

The environment is likely affected if Crafter CMS version 3.1.0 through 3.1.17 is installed, developer or admin accounts exist, and FreeMarker template functionality is accessible to those accounts.

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.18 or later
Fixed in 3.1.18
Interim mitigation

Restrict or disable OS command execution capabilities in FreeMarker templates, apply principle of least privilege to developer accounts, and upgrade to the patched Crafter CMS version.

Recommended fix High confidence

3.1.18

  1. 1. Back up your current Crafter CMS installation and database before upgrading.
  2. 2. Download Crafter CMS version 3.1.18 from the official Crafter CMS downloads page (downloads.craftercms.org).
  3. 3. Stop the Crafter Studio service.
  4. 4. Run the upgrade script or replace the Crafter Studio application files with the 3.1.18 version.
  5. 5. Verify the upgrade by logging into Crafter Studio as an authenticated developer.
  6. 6. Confirm the FreeMarker static methods that could allow OS command execution are now properly restricted.

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 / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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