dbcve.org
CWE-1321Weakness · CWE-1321

CVE-2026-54756

MEDIUM · 6.3 CVSS v4.0 Published 2026-07-01
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click 8 weeks old

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
Jodit Editor is a WYSIWYG editor with written in pure TypeScript file and image editing capabilities. In versions prior to 4.12.18, Jodit.configure(options) — and the internal ConfigMerge / ConfigProto helpers — merged user-supplied options into the editor configuration without filtering prototype-mutating keys, potentially causing a Prototype Pollution vulnerability. A payload nested under an existing plain-object option such as controls could reach and mutate Object.prototype. Applications that pass user-controlled or partially user-controlled configuration into Jodit.configure() may be vulnerable. This issue was fixed in version 4.12.18.

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

Jodit Editor versions before 4.12.18 contain a Prototype Pollution vulnerability in Jodit.configure() and the ConfigMerge/ConfigProto helpers. These functions merge user-supplied options into the editor configuration without filtering prototype-mutating keys (e.g., __proto__, constructor). A malicious payload nested under an existing plain-object option like 'controls' can reach and mutate Object.prototype, potentially leading to arbitrary code execution or security bypasses.

MitigationUpgrade Jodit Editor to version 4.12.18 or later. If upgrading is not immediately feasible, sanitize all user-supplied configuration options before passing them to Jodit.configure() by filtering keys like __proto__, constructor, and prototype.

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
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 the installed Jodit Editor version
    Check your package.json, node_modules/jodit/package.json, or the Jodit source file for the version field. Compare it to the affected range: any version before 4.12.18 is vulnerable.
    Affected if The installed version is lower than 4.12.18
  2. Locate calls to Jodit.configure() in your codebase
    Search your codebase for Jodit.configure( patterns and inspect whether the configuration object contains any user-supplied input, such as request parameters, form data, or API payloads merged into the options.
    Affected if Jodit.configure() receives options derived from untrusted user input
  3. Inspect configuration merging for prototype-mutating keys
    Examine any code that passes user-controlled objects into Jodit's configuration. Look for the presence of keys named __proto__, constructor, or prototype nested within object options like controls, buttons, or other plain-object configuration properties.
    Affected if User-supplied options containing __proto__, constructor, or prototype keys are merged into the configuration
  4. Review usage of ConfigMerge or ConfigProto helpers
    Search for imports or usage of ConfigMerge, ConfigProto, or similar helper functions from Jodit. Determine whether these helpers process untrusted configuration data.
    Affected if ConfigMerge or ConfigProto helpers process untrusted configuration objects

You are affected if you run any Jodit Editor version before 4.12.18 and your application passes user-supplied data to Jodit.configure() or related helpers without filtering prototype-mutating keys.

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 Jodit Editor to version 4.12.18 or later. If upgrading is not immediately feasible, sanitize all user-supplied configuration options before passing them to Jodit.configure() by filtering keys like __proto__, constructor, and prototype.

Recommended fix High confidence

4.12.18

  1. Identify the current Jodit Editor version used in your project (check package.json or node_modules/jodit/package.json).
  2. Update the Jodit dependency to version 4.12.18 or later. For npm, run: npm install jodit@^4.12.18 (or npm update jodit).
  3. Run npm install to ensure the new version is fully resolved and installed.
  4. Verify the installed version with npm list jodit to confirm you are on 4.12.18 or higher.
  5. Test the application to ensure the editor functions correctly and that the prototype‑pollution vulnerability is mitigated.
Caveat None documented; review release notes if upgrading from very old versions.

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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