CVE-2023-48219
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 0.72 % · percentile 54.30 % · scored 15 Nov 2026.
Saved 15 Nov 2026 14:45:34 UTC · View this risk record (JSON)
No access to your tenant or devices. Every item links to its source. What this means
TinyMCE is an open source rich text editor. A mutation cross-site scripting (mXSS) vulnerability was discovered in TinyMCE’s core undo/redo functionality and other APIs and plugins. Text nodes within specific parents are not escaped upon serialization according to the HTML standard. If such text nodes contain a special character reserved as an internal marker, they can be combined with other HTML patterns to form malicious snippets. These snippets pass the initial sanitisation layer when the content is parsed into the editor body, but can trigger XSS when the special internal marker is removed from the content and re-parsed. his vulnerability has been patched in TinyMCE versions 6.7.3 and 5.10.9. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Read the publisher's advisoryTinyMCE is an open source rich text editor. A mutation cross-site scripting (mXSS) vulnerability was discovered in TinyMCE’s core undo/redo functionality and other APIs and plugins. Text nodes within specific parents are not escaped upon serialization according to the HTML standard. If such text nodes contain a special character reserved as an internal marker, they can be combined with other HTML patterns to form malicious snippets. These snippets pass the initial sanitisation layer when the content is parsed into the editor body, but can trigger XSS when the special internal marker is removed from the content and re-parsed. his vulnerability has been patched in TinyMCE versions 6.7.3 and 5.10.9. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Read the publisher's advisoryTinyMCE is an open source rich text editor. A mutation cross-site scripting (mXSS) vulnerability was discovered in TinyMCE’s core undo/redo functionality and other APIs and plugins. Text nodes within specific parents are not escaped upon serialization according to the HTML standard. If such text nodes contain a special character reserved as an internal marker, they can be combined with other HTML patterns to form malicious snippets. These snippets pass the initial sanitisation layer when the content is parsed into the editor body, but can trigger XSS when the special internal marker is removed from the content and re-parsed. his vulnerability has been patched in TinyMCE versions 6.7.3 and 5.10.9. Users are advised to upgrade. There are no known workarounds for this vulnerability.
Read the publisher's advisory### Impact A [mutation cross-site scripting](https://researchgate.net/publication/266654651_mXSS_attacks_Attacking_well-secured_web-applications_by_using_innerHTML_mutations) (mXSS) vulnerability was discovered in TinyMCE’s core undo/redo functionality and other APIs and plugins. Text nodes within specific parents are not escaped upon serialization according to the [HTML standard](https://html.spec.whatwg.org/multipage/parsing.html#serialising-html-fragments). If such text nodes contain a special character reserved as an internal marker, they can be combined with other HTML patterns to form malicious snippets. These snippets pass the initial sanitisation layer when the content is parsed into the editor body, but can trigger XSS when the special internal marker is removed from the content and re-parsed. Such mutations occur when serialised HTML content is processed before being stored in the undo stack, or when the following APIs and plugins are used: * [`tinymce.Editor.getContent({ format: 'raw' })`](https://tiny.cloud/docs/tinymce/6/apis/tinymce.editor/#getContent) * [`tinymce.Editor.resetContent()`](https://tiny.cloud/docs/tinymce/6/apis/tinymce.editor/#resetContent) * [Autosave Plugin](https://tiny.cloud/docs/tinymce/6/autosave/) ### Patches This vulnerability has been patched in TinyMCE 6.7.3 by: * ensuring that any unescaped text nodes which contain the special internal marker are emptied before removing the marker from the rest of the HTML, and * removing the special internal marker from content strings passed to `Editor.setContent`, `Editor.insertContent`, and `Editor.resetContent` APIs to prevent them from being loaded into the editor as user-provided content. ### Fix To avoid this vulnerability: - Upgrade to TinyMCE 6.7.3 or higher for TinyMCE 6.x. - Upgrade to TinyMCE 5.10.9 or higher for TinyMCE 5.x. ### Acknowledgements Tiny Technologies would like to thank Masato Kinugawa of [Cure53](https://cure53.de/) for discovering this vulnerability. ### References - [TinyMCE 5.10.9 Release Notes](https://tiny.cloud/docs/release-notes/release-notes5109/) - [TinyMCE 6.7.3 Release Notes](https://tiny.cloud/docs/tinymce/6/6.7.3-release-notes/) ### For more information Email us at [[email protected]](mailto:[email protected]) Open an issue in the [TinyMCE repo](https://github.com/tinymce/tinymce/issues?q=is%3Aissue+is%3Aopen+sort%3Aupdated-desc)
Read the publisher's advisoryCISA KEV lists vulnerabilities known to be exploited. FIRST EPSS estimates the likelihood of exploitation in the next 30 days. An unavailable score does not mean zero risk.
This view includes predictions for CVE identifiers explicitly listed in public NuGet advisories. Microsoft release pages have their own prediction coverage. Check source status for the scope and latest checks.
No CISA KEV listing is included in this saved record. Exploitation may still have occurred.
FIRST EPSS: 0.72 % · percentile 54.30 % · scored 15 Nov 2026.
Saved 15 Nov 2026 14:45:34 UTC · View this risk record (JSON)
Compare earlier KEV listings and EPSS scores. Advisory wording and affected versions have a separate history.
A prediction change is reported when EPSS rises from below 10% to 10% or higher. Every daily score change from the last 30 days stays in this history. Before that, it keeps KEV changes and moves between EPSS bands (0.1%, 1%, 5%, 10%, 20%, 50% and 90%).
CVE-2023-48219 · 15 Nov 2026 14:45:34 UTC
CVE-2023-48219 · 14 Nov 2026 16:37:01 UTC
CVE-2023-48219 · 13 Nov 2026 19:59:34 UTC
CVE-2023-48219 · 12 Nov 2026 18:18:51 UTC
CVE-2023-48219 · 10 Nov 2026 20:24:10 UTC
CVE-2023-48219 · 09 Nov 2026 21:04:24 UTC
CVE-2023-48219 · 08 Nov 2026 15:12:21 UTC
CVE-2023-48219 · 07 Nov 2026 16:07:52 UTC
CVE-2023-48219 · 06 Nov 2026 19:10:17 UTC
CVE-2023-48219 · 05 Nov 2026 22:49:22 UTC
CVE-2023-48219 · 05 Nov 2026 02:54:06 UTC
CVE-2023-48219 · 03 Nov 2026 16:59:18 UTC
CVE-2023-48219 · 02 Nov 2026 23:59:04 UTC
CVE-2023-48219 · 01 Nov 2026 23:58:58 UTC
CVE-2023-48219 · 01 Nov 2026 03:04:52 UTC
CVE-2023-48219 · 31 Oct 2026 01:52:30 UTC
CVE-2023-48219 · 29 Oct 2026 18:29:26 UTC
CVE-2023-48219 · 28 Oct 2026 19:55:37 UTC
CVE-2023-48219 · 27 Oct 2026 15:46:19 UTC
CVE-2023-48219 · 27 Oct 2026 00:23:05 UTC
CVE-2023-48219 · 25 Oct 2026 15:18:41 UTC
See how the publisher's advisory changed over time. Each link opens the version saved at that time. The publisher's update date can differ from the date shown here.
Each link identifies one complete publisher record. History can include advisories that previously shared an identifier; an identifier removed by a publisher no longer establishes a current relationship. A historical link shows only that record and earlier saved versions. Failed checks and unchanged reads do not create new versions.
euvd · EUVD-2023-3037 · Published
euvd · EUVD-2023-3037 · Published
euvd · EUVD-2023-3037 · Published
euvd · EUVD-2023-3037 · Published
euvd · EUVD-2023-3037 · Published
euvd · EUVD-2023-3037 · Published
euvd · EUVD-2023-3037 · Published
euvd · EUVD-2023-3037 · Published
euvd · EUVD-2023-3037 · Published
euvd · EUVD-2023-3037 · Published
nvd · CVE-2023-48219 · Published
osv · GHSA-v626-r774-j7f8 · Published
cve-program · CVE-2023-48219 · Published