dbcve.org
Crafter CmsApplication · Craftercms

CVE-2021-23262

HIGH · 7.2 CVSS v3.1 Published 2021-12-02
Fix available
A fix is available. Upgrade to 3.1.13 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
Authenticated administrators may modify the main YAML configuration file and load a Java class resulting in RCE.

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

Authenticated administrators can modify the main YAML configuration file to load an arbitrary Java class, enabling remote code execution. This stems from insecure deserialization or class loading from YAML configuration.

MitigationRestrict administrative access, implement strict validation on YAML-parsed class references, and apply vendor patches. Consider disabling dynamic class loading from configuration files.

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.13

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. Check CrafterCMS version
    Locate and read the version file or use the management interface to determine the installed CrafterCMS version. Common locations include version.properties or the about page in the admin console.
    Affected if The installed version is 3.1.0 through 3.1.12 (any version >= 3.1.0 and < 3.1.13)
  2. Identify the main YAML configuration file
    Locate the primary YAML configuration file that CrafterCMS uses for application settings. This is typically found in the installation directory under config or similar folders.
    Affected if The YAML configuration file exists and is writable by the application user
  3. Inspect YAML for unsafe class loading patterns
    Examine the main YAML configuration file for elements that load Java classes dynamically, such as spring bean definitions with custom class attributes, script executors, or deserialization configurations that accept user-controlled class references.
    Affected if The YAML config contains class, bean, or script definitions that reference arbitrary or unexpected Java class names
  4. Verify dynamic class loading is enabled
    Search the configuration for settings that enable dynamic class loading, deserialization from YAML, or script execution from configuration. Look for flags like enableBeans, allowDynamicClassLoading, or similar features.
    Affected if Dynamic class loading or unsafe deserialization is enabled in the configuration
  5. Confirm administrative access to configuration
    Determine if the administrative interface or configuration files are accessible to authenticated administrators who could modify the YAML configuration.
    Affected if Authenticated administrators have write access to the main YAML configuration file

You are affected if your CrafterCMS version is 3.1.0 through 3.1.12 AND the main YAML configuration can be modified by an authenticated administrator to inject arbitrary Java class references.

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.13 or later
Fixed in 3.1.13
Interim mitigation

Restrict administrative access, implement strict validation on YAML-parsed class references, and apply vendor patches. Consider disabling dynamic class loading from configuration files.

Recommended fix Moderate confidence

Crafter CMS 3.1.13 or later

  1. Download Crafter CMS version 3.1.13 or later from the official Crafter CMS downloads page
  2. Ensure you have a complete backup of your current installation including the data and config directories
  3. Stop the Crafter CMS services
  4. Replace the existing Crafter CMS installation files with the new version files
  5. Restore your configuration and data from the backup
  6. Start the Crafter CMS services and verify the application runs correctly
  7. Verify that the security fix is applied by confirming the YAML configuration no longer allows arbitrary Java class loading
Caveat Review the release notes for 3.1.13 to check for any configuration changes or migration requirements that may affect your setup

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-23262 — 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-23262 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