Threats affecting pkg:npm/tinymce

A stored cross-site scripting (XSS) vulnerability exists in the media plugin of TinyMCE. Attackers can inject malicious scripts via crafted data-mce-* attributes, which execute when the content is rendered. This affects users of TinyMCE with the media plugin enabled. The vulnerability has been patched in TinyMCE versions 8.5.1, 7.9.3, and 5.11.1 LTS. No official workaround is available other than upgrading to a fixed version.

A stored cross-site scripting (XSS) vulnerability exists in TinyMCE through forged mce:protected comments. This flaw allows attackers to bypass sanitization and inject malicious scripts that execute when the protected content is restored. The vulnerability affects users who utilize the protect option in TinyMCE. No official workaround is available. The issue is fixed by validating decoded mce:protected content against configured protect regex rules before restoration. Users should upgrade to TinyMCE 8.5.1 or higher, 7.9.3 or higher, or 5.11.1 LTS or higher (the latter requires a commercial support contract).

TinyMCE versions up to 5.10.9, from 6.0.0 up to but not including 7.9.3, and from 8.0.0 up to but not including 8.5.1 are affected by a stored Cross-Site Scripting (XSS) vulnerability. The issue arises from unsanitized data-mce-* attributes (specifically data-mce-href, data-mce-src, and data-mce-style) that allow attackers to inject malicious content bypassing validation during serialization. This vulnerability has been patched by stripping unsafe data-mce-* attributes during parsing. Users should upgrade to TinyMCE 8.5.1 or higher, 7.9.3 or higher, or 5.11.1 LTS or higher (the latter available only under commercial long-term support). No official workaround is available.

TinyMCE versions before 5.6.0 are affected by a stored cross-site scripting vulnerability. An unauthenticated and remote attacker could insert crafted HTML into the editor resulting in arbitrary JavaScript execution in another user's browser.

TinyMCE versions before 5.9.0 are affected by a stored cross-site scripting vulnerability. An unauthenticated and remote attacker could insert crafted HTML into the editor resulting in arbitrary JavaScript execution in another user's browser.