Track vulnerabilities like this one. Sign up free to get alerted when software you use is affected.
8.4

Jodit Editor can be tricked into altering global objects

CVE-2026-54756 · published 4 months ago
Summary

Versions of Jodit Editor before 4.12.18 let custom settings merge unchecked data into the editor’s core configuration. If a web application passes user‑controlled options to Jodit.configure(), an attacker could change basic JavaScript objects and affect the whole page. Upgrade Jodit Editor to version 4.12.18 or later, or avoid accepting untrusted configuration input.

What to do
  • Update GitHub Actions jodit to version 4.12.18.
Affected software
Ecosystem VendorProductAffected versions
npm GitHub Actions jodit < 4.12.18
Fix: upgrade to 4.12.18
Original advisory text
Jodit Editor: Prototype pollution via Jodit.configure() / ConfigMerge
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.
References
Fix within
Internet-facing 14 days
Internal At next upgrade
  • Not known to be exploited
  • Needs hands-on effort to exploit
  • Gives an attacker full control
Severity
8.4 High
Exploitation
<1% chance of attack within 30 days
Type
CWE-1321Prototype Pollution
Timeline
Published1 Jul 2026
Updated4 Nov 2026
First seen1 Jul 2026
Sources
CVE-2026-54756 · NVD
GHSA-5957-5c94-3v7w · GHSA
GHSA-5957-5c94-3v7w · OSV
CVE-2026-54756 · OSV
Track software like this
Free during beta