dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-58263

HIGH · 7.2 CVSS v3.1 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 →
81/100
Remediation priority · High
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 a built-in file browser & image editor. In versions prior to 4.12.28, the built-in clean-html sanitizer can be bypassed by a MathML/<style> carrier that hides a dangerous element from the sanitizer's element walk, so a no-interaction event handler survives into the editor value, potentially causing Mutation XSS. When an application supplies attacker-influenced HTML to the editor's value-set or insertion paths, the sanitized output still contains a live <img ... onload=...> (or another non-onerror handler such as onfocus). A consumer that renders that output (element.innerHTML = editor.value) executes the handler with no user interaction. This issue has been fixed in version 4.12.28.

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's clean-html sanitizer can be bypassed using MathML/<style> constructs that hide malicious elements (specifically event handlers like onload or onfocus) from the sanitizer's element walk. This Mutation XSS allows no-interaction execution when the sanitized output is rendered via innerHTML.

MitigationUpgrade Jodit Editor to version 4.12.28 or later to patch the sanitizer bypass. Additionally, validate that any downstream rendering of editor output uses safe DOM methods (e.g., textContent) or additional output sanitization.

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
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N

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 Jodit Editor installation
    Search your codebase, dependencies, or web application for Jodit Editor files (typically in node_modules/jodit, bower_components/jodit, or loaded via CDN). Check package.json, package-lock.json, or similar dependency files for @jodit/editor or jodit packages.
    Affected if Jodit Editor is present in the environment
  2. Determine Jodit Editor version
    Examine the installed version from package.json, package-lock.json, or the jodit.min.js/jodit.js file header. Look for a version string like '4.x.x'.
    Affected if Version is below 4.12.28 (e.g., 4.12.27, 4.11.x, 4.10.x, etc.)
  3. Confirm clean-html sanitizer is in use
    Review your Jodit Editor configuration. The clean-html sanitizer is enabled by default. Check if you have custom sanitize configuration or if default sanitization is in place. Look for options like sanitize: true or cleaner settings in your editor initialization.
    Affected if Default sanitization is active (the default behavior)
  4. Check output rendering method
    Search your codebase where Jodit Editor content is displayed. Look for uses of innerHTML, outerHTML, or document.write to render the sanitized HTML output. Also check if Content-Security-Policy headers restrict unsafe-inline.
    Affected if Editor output is rendered using innerHTML or outerHTML without additional output encoding

You are affected if Jodit Editor version is below 4.12.28 AND the clean-html sanitizer is enabled AND the sanitized output is rendered via innerHTML, allowing event handlers hidden in MathML/style constructs to execute.

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.28 or later to patch the sanitizer bypass. Additionally, validate that any downstream rendering of editor output uses safe DOM methods (e.g., textContent) or additional output sanitization.

Recommended fix High confidence

4.12.28

  1. Upgrade Jodit Editor to version 4.12.28 or later to resolve the Mutation XSS vulnerability in the clean-html sanitizer
  2. After upgrading, verify that user-supplied HTML is properly sanitized and does not contain any event handlers (onload, onfocus, etc.) in the sanitized output
  3. If using a package manager, update the dependency: npm install jodit@^4.12.28 or yarn add jodit@^4.12.28
  4. Test the editor's value-set and insertion paths to confirm the sanitization properly blocks event handlers
  5. Verify that any downstream consumers of editor value (e.g., element.innerHTML = editor.value) do not execute any injected event handlers

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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