Jodit Editor: Mutation XSS in jodit clean-html via a MathML/style rawtext carrier

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-58263: 0.22% estimated exploitation activity in the next 30 days; percentile 12.04 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary jodit's 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. 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 is a stored cross-site scripting vulnerability, confirmed live on the shipped es2021/jodit.min.js for 4.12.25 and the latest 4.12.27 (in Chromium via a client-side innerHTML consumer, and in Firefox via server-rendered / document-context output; see the cross-browser note under Proof of concept). Details The bypass exploits the order in which clean-html parses, walks, and re-serializes the value. 1. On the value-set path, the clean-html…

Published by the source

31 Jul 2026, 19:12 UTC

Last modified by the source

31 Jul 2026, 19:12 UTC

Source last checked

26 Oct 2026, 13:00 UTC

1. Revision 1 · created · 26 Oct 2026

   Published from ghsa record GHSA-rxcw-mc6f-6hr3

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-58263

Advisory: Jodit Editor: Mutation XSS in jodit clean-html via a MathML/style rawtext carrier
IDs: CVE-2026-58263, GHSA-rxcw-mc6f-6hr3
Record: https://patchnext.com/advisories/cve-2026-58263 (revision 1, source checked 26 Oct 2026, 13:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: High (CVSS 7.2)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: jodit 4.12.28. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm jodit: affected < 4.12.28; fixed in 4.12.28

## Suggested inspection (read-only)
- `npm ls jodit --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on jodit.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-rxcw-mc6f-6hr3 (GitHub-reviewed advisory GHSA-rxcw-mc6f-6hr3 lists affected ranges: npm jodit >=0 <4.12.28)

Commands are suggestions: review each one before running it.