dbcve.org
Code InjectionWeakness · CWE-94

CVE-2026-56382

HIGH · 7.2 CVSS v3.1 Published 2026-06-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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
Craft CMS (composer package craftcms/cms) versions >= 5.5.0 and <= 5.9.13 contain a remote code execution vulnerability in the FieldsController::actionRenderCardPreview() method, which passes the fieldLayoutConfig POST parameter directly to Fields::createLayout() without calling Component::cleanseConfig(). An authenticated admin user can inject Yii2 event handlers (e.g., 'on init' keys) via the fieldLayoutConfig parameter to execute arbitrary PHP code and disclose sensitive information (such as environment variables containing database credentials and CRAFT_SECURITY_KEY). The issue is fixed in version 5.9.14.

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

Craft CMS versions 5.5.0 through 5.9.13 contain an authenticated RCE vulnerability in FieldsController::actionRenderCardPreview(). The fieldLayoutConfig POST parameter is passed directly to Fields::createLayout() without sanitization via Component::cleanseConfig(), allowing authenticated admin users to inject Yii2 event handlers (e.g., 'on init' keys) to achieve arbitrary PHP code execution and exfiltrate sensitive environment variables including database credentials and CRAFT_SECURITY_KEY.

MitigationUpgrade Craft CMS to version 5.9.14 or later. If immediate upgrade is not possible, restrict admin user access and monitor for suspicious fieldLayoutConfig POST requests.

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

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 Craft CMS version
    Locate the Craft CMS version by checking composer.json in the project root, or log into the admin control panel and navigate to Utilities > System Report to view the version number.
    Affected if The installed version falls within the range 5.5.0 through 5.9.13 (inclusive).
  2. Verify admin user access exists
    Review user accounts in the Craft CMS admin panel under Users section. Check which users are assigned to the Admin group or have super admin privileges.
    Affected if Any user with admin-level privileges exists in the system, as the vulnerability requires an authenticated admin session.
  3. Inspect web server access logs for suspicious requests
    Search access logs (typically in /var/log/nginx/ or /var/log/apache2/) for POST requests to /actions/fields/fields/render-card-preview or similar paths containing 'fields/render-card-preview'.
    Affected if Any POST requests are observed with the fieldLayoutConfig parameter containing Yii2 event handler syntax such as 'on init', 'on run', or similar keys that do not match normal Craft configuration patterns.
  4. Review application logs for field layout errors
    Check Craft CMS logs in storage/logs/ for exceptions or errors related to Fields::createLayout or Component::cleanseConfig that may indicate exploitation attempts.
    Affected if Errors appear related to malformed fieldLayoutConfig data or unexpected component initialization patterns.

A user is affected if they run Craft CMS version 5.5.0 through 5.9.13 AND have any admin user account present in the system, allowing the fieldLayoutConfig parameter in a POST request to trigger code execution.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Craft CMS to version 5.9.14 or later. If immediate upgrade is not possible, restrict admin user access and monitor for suspicious fieldLayoutConfig POST requests.

Recommended fix High confidence

5.9.14 (or latest 5.9.x release)

  1. Verify current Craft CMS version by checking composer.json or the control panel version number
  2. Backup the database and all files before upgrading
  3. Run composer update craftcms/cms:5.9.14 to install the fixed version, or composer require craftcms/cms:^5.9.14 to upgrade to the latest 5.9.x release
  4. Clear caches after upgrade by running php craft clear-caches/all from the web root
  5. Verify the upgrade was successful by checking the version in the control panel
  6. Ensure the admin user account used to trigger the vulnerability has appropriate permissions
Caveat Review the Craft CMS 5.9.14 release notes for any breaking changes between your current version and 5.9.14, particularly if upgrading from versions before 5.8.0

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing8.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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