CVE-2026-58263

HIGHPre-NVD 7.27.2—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.2 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 92% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.2
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 7.2Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Jodit Editor is a WYSIWYG editor with written in pure TypeScript file and image editing capabilities. In versions prior to 4.12.28, the built-in clean-html sanitizer can be bypassed by a MathML/ 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 (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.

CVSS v3
7.2
EG Score
7.2(medium)
EPSS
7.6%
KEV
Not listed

Published

July 1, 2026

Last Modified

July 2, 2026

Advisory Details (1)

Auto-updated Jul 1, 2026
🔬 Proof of concept available. Patch available. Sources: github.
github Patch Available🟡 PoC Available

Mutation XSS in jodit clean-html via a MathML/style rawtext carrier · Advisory · xdan/jodit · GitHub

https://github.com/xdan/jodit/security/advisories/GHSA-rxcw-mc6f-6hr3

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 28× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-11 18:56 UTCEG score recompute
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-11 08:27 UTCEPSS rescore
  4. 2026-07-11 06:33 UTCEG score recompute
  5. 2026-07-10 18:09 UTCEG score recompute
  6. 2026-07-10 05:45 UTCEG score recompute
  7. 2026-07-09 19:10 UTCEPSS rescore
  8. 2026-07-09 19:10 UTCEPSS rescore
  9. 2026-07-09 17:21 UTCEG score recompute
  10. 2026-07-09 04:55 UTCEG score recompute
  11. 2026-07-08 16:31 UTCEG score recompute
  12. 2026-07-08 15:16 UTCEPSS rescore
  13. 2026-07-08 15:16 UTCEPSS rescore
  14. 2026-07-08 04:08 UTCEG score recompute
  15. 2026-07-07 15:43 UTCEG score recompute
  16. 2026-07-07 13:46 UTCEPSS rescore
  17. 2026-07-07 13:46 UTCEPSS rescore
  18. 2026-07-07 03:18 UTCEG score recompute
  19. 2026-07-06 16:27 UTCEPSS rescore
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 14:55 UTCEG score recompute
  22. 2026-07-06 02:28 UTCEG score recompute
  23. 2026-07-06 02:23 UTCEPSS rescore
  24. 2026-07-06 02:23 UTCEPSS rescore
  25. 2026-07-05 14:04 UTCEG score recompute
Show 12 more
  1. 2026-07-05 02:31 UTCEPSS rescore
  2. 2026-07-05 02:30 UTCEPSS rescore
  3. 2026-07-05 01:36 UTCEG score recompute
  4. 2026-07-04 13:11 UTCEG score recompute
  5. 2026-07-04 06:31 UTCEPSS rescore
  6. 2026-07-04 06:31 UTCEPSS rescore
  7. 2026-07-04 00:46 UTCEG score recompute
  8. 2026-07-03 12:23 UTCEG score recompute
  9. 2026-07-02 23:58 UTCEG score recompute
  10. 2026-07-02 11:35 UTCEG score recompute
  11. 2026-07-01 23:10 UTCEG score recompute
  12. 2026-07-01 23:08 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-58263?
CVE-2026-58263 is a high vulnerability published on July 1, 2026. Jodit Editor is a WYSIWYG editor with written in pure TypeScript file and image editing capabilities. 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…
When was CVE-2026-58263 disclosed?
CVE-2026-58263 was first published in the National Vulnerability Database on July 1, 2026, with the most recent update on July 2, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-58263 actively exploited?
CVE-2026-58263 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 7.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-58263?
CVE-2026-58263 has a CVSS v3 base score of 7.2 (NVD).
How do I remediate CVE-2026-58263?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-58263, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-58263

Explore →

Is Your Infrastructure Affected by CVE-2026-58263?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs