Skip to main content
VulnerabilityPublished

CVE-2026-54756: xdan jodit · Prototype Pollution

Affects xdan joditSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 6.3 Medium : upgrade to 4.12.18 when convenient.

Data as of 12 Nov 2026, 23:24 UTC

CVSS 4.0 base score
6.3Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.12.18
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 1 Jul 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 13 Nov 2026.

What to do

Upgrade xdan jodit to 4.12.18.

Affected software

ProductAffectedFixed in
xdanjoditAffected
  • <4.12.18
Fixed in
  • 4.12.18
npmjoditpkg:npm/joditOther threatsAffected
  • <4.12.18
Fixed in
  • 4.12.18

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A patch is available and was released in Jodit version 4.12.18. Users should upgrade to version 4.12.18 or later to mitigate this vulnerability. The fix rejects the prototype-mutating keys (__proto__, constructor, prototype) at every merge level in the configuration process. No additional mitigation steps are required if the upgrade is applied.

Description

Jodit versions prior to 4.12.18 contain a prototype pollution vulnerability in the Jodit.configure(options) API. The vulnerability arises because user-supplied options are merged into the editor configuration without filtering keys that can mutate Object.prototype. This allows an attacker to inject properties into Object.prototype, potentially causing unexpected behavior, logic bypass, denial of service, or other security issues. The issue was fixed in version 4.12.18 by rejecting prototype-mutating keys during configuration merges.

References

Community reviews

Loading reviews…