CVE-2026-6224
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 · uneditedA security flaw has been discovered in nocobase plugin-workflow-javascript up to 2.0.23. This issue affects the function createSafeConsole of the file packages/plugins/@nocobase/plugin-workflow-javascript/src/server/Vm.js. Performing a manipulation results in sandbox issue. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. The vendor was contacted early about this disclosure but did not respond in any way.
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 confidenceA sandbox escape vulnerability exists in the nocobase plugin-workflow-javascript (versions up to 2.0.23) within the createSafeConsole function in Vm.js. This allows remote attackers to bypass the JavaScript sandbox isolation and potentially execute arbitrary code on the server by manipulating the console object that is intended to provide safe, restricted access to JavaScript execution contexts.
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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 checksWork through these to decide whether this CVE applies to you.
-
Verify plugin-workflow-javascript is installedList installed NocoBase plugins by checking the plugin configuration file (typically in /packages/plugins/ or the nocobase configuration) or run: npm list @nocobase/plugin-workflow-javascriptAffected if The plugin appears in the installed plugins list
-
Check the installed plugin versionRun: npm list @nocobase/plugin-workflow-javascript or inspect package.json in the plugin directory to find the version numberAffected if The version is 2.0.23 or lower
-
Confirm JavaScript workflow feature is enabledCheck NocoBase admin settings or configuration file for workflow plugin status. Look for workflow-javascript or javascript workflow entries in the enabled plugins or features listAffected if The JavaScript workflow feature is listed as enabled or active
-
Verify vulnerable Vm.js file existsLocate the plugin-workflow-javascript installation directory and confirm the presence of Vm.js containing the createSafeConsole function (typically in src/ directory)Affected if The file Vm.js with createSafeConsole function is present in the plugin installation
A user is affected if the plugin-workflow-javascript is installed with version 2.0.23 or lower and the JavaScript workflow feature is enabled, allowing workflow execution that can leverage the vulnerable sandbox escape in Vm.js
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataUpgrade the plugin-workflow-javascript to a version beyond 2.0.23 when available. As an interim measure, disable the plugin or restrict access to workflow execution features until a patch is applied.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
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 locallyCheck whether your project pulls in CVE-2026-6224 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-6224 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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