dbcve.org
Crafter CmsApplication · Craftercms

CVE-2023-26020

HIGH · 7.2 CVSS v3.1 Published 2023-02-17
Fix available
A fix is available. Upgrade to after 4.0.1 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 Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Crafter Studio on Linux, MacOS, Windows, x86, ARM, 64 bit allows SQL Injection.This issue affects CrafterCMS v4.0 from 4.0.0 through 4.0.1, and v3.1 from 3.1.0 through 3.1.26.

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

SQL injection vulnerability in Crafter Studio allows attackers to inject malicious SQL commands through unsanitized input fields in database queries, potentially enabling unauthorized data exfiltration, modification, or database compromise.

MitigationUpgrade to CrafterCMS v4.0.2+ or v3.1.27+ to obtain the patched version, or implement parameterized queries and proper input validation on affected SQL queries.

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.26>= 4.0.0, <= 4.0.1

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 CrafterCMS installation and version
    Check the version file typically located in the CrafterCMS installation directory, such as ./crafter/bin/version.sh or look for a version.properties file in the CrafterCMS root directory. You can also check the Crafter Studio login page footer which often displays the version number.
    Affected if The installed version falls within 3.1.0 to 3.1.26 or 4.0.0 to 4.0.1.
  2. Confirm Crafter Studio is accessible
    Verify that Crafter Studio web interface is accessible by attempting to reach the Studio endpoint (typically /studio or the main application URL). Check if the studio web application is deployed and running.
    Affected if Crafter Studio is exposed and running on a version within the affected ranges.
  3. Identify database configuration
    Locate the database configuration file, typically found in CrafterCMS installation under ./crafter/data/repos/sites/{site-name}/config/studio/database-config.groovy or the main configuration at ./crafter/bin/crafter-setenv.sh to identify the database type and connection settings.
    Affected if The database is configured and accessible to Crafter Studio, which is the default configuration for affected versions.
  4. Audit custom Crafter scripts or plugins
    Review any custom Groovy scripts, plugins, or extensions installed in ./crafter/data/repos/sites/{site-name}/scripts or ./crafter/plugins for database query logic that may be vulnerable to SQL injection through user input.
    Affected if Custom scripts or plugins exist that construct SQL queries using user-supplied input without proper parameterization.

You are affected if CrafterCMS version is 3.1.0-3.1.26 or 4.0.0-4.0.1 AND Crafter Studio is accessible and configured to use a database.

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 a release after 4.0.1
Interim mitigation

Upgrade to CrafterCMS v4.0.2+ or v3.1.27+ to obtain the patched version, or implement parameterized queries and proper input validation on affected SQL queries.

Recommended fix Moderate confidence

CrafterCMS 4.0.2 or later (4.x branch); CrafterCMS 3.1.27 or later (3.1 branch)

  1. 1. Backup your current CrafterCMS installation and database before proceeding
  2. 2. Download the fixed version of CrafterCMS (4.0.2 or later for the 4.x branch, 3.1.27 or later for the 3.1 branch) from the official CrafterCMS downloads page at docs.craftercms.org
  3. 3. Stop the CrafterCMS services running on your server
  4. 4. Follow the official upgrade instructions for your specific version path (3.1.x to 3.1.27+ or 4.0.x to 4.0.2+) from the CrafterCMS documentation
  5. 5. Verify the upgrade was successful by logging into Crafter Studio and confirming all sites are accessible
  6. 6. Test that the SQL injection vulnerability is remediated by attempting the previously vulnerable operation
Caveat Review the release notes for the intermediate versions between your current version and the target fixed version for any configuration or feature changes that may require adjustments

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-2023-26020 — 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-2023-26020 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