CVE-2026-116675: TinyMCE Cross-Site Scripting (XSS) vulnerability using media plugin `data-mce-object` serialization
CVE-2026-116675 is a stored cross-site scripting flaw in the TinyMCE media plugin. An attacker can plant script in content through the data-mce-object attribute, and it runs in the browser of whoever views or edits that content. Fixed in TinyMCE 8.9.3 and 7.9.4. Only installs with the media plugin enabled are affected.
Published Oct 27, 2026 · Analysis Nov 1, 2026
What an attacker can do
TinyMCE's media plugin turns media elements into placeholder objects marked with the data-mce-object attribute. The advisory says elements crafted through that attribute are created and executed before sanitization runs. The release notes add that event handler scripts on those elements could fire. The fix makes the plugin sanitize content created through data-mce-object first.
The attack needs an account that can save content into an editor field (CVSS PR:L) and a victim who loads it (UI:P). The script then runs in the victim's session on your site: it can read page data, act as the victim, and, if the victim is an administrator, take over that account. This matters most for CMS, wiki, ticketing and comment systems where one user's rich text is opened by another. The CVSS 4.0 vector rates confidentiality and integrity impact high.
Who is affected
TinyMCE with the media plugin enabled, in these versions: 8.5.1 up to but not including 8.9.3, and exactly 7.9.3. This covers the npm tinymce, NuGet TinyMCE and Composer tinymce/tinymce packages.
Check your version:
npm ls tinymceThen look in your editor init code for "media" in the plugins list. If it is absent, the vulnerable path is not loaded. Self-hosted copies and bundled front-end builds need a check of the shipped TinyMCE files.
tinymce
- Ecosystem
- npm
- Affected
- >= 8.5.1, < 8.9.3
- Fixed in
- 8.9.3
- Check
npm ls tinymce
TinyMCE
- Ecosystem
- NuGet
- Affected
- >= 8.5.1, < 8.9.3
- Fixed in
- 8.9.3
- Check
dotnet list package --include-transitive
tinymce/tinymce
- Ecosystem
- Composer (PHP)
- Affected
- >= 8.5.1, < 8.9.3
- Fixed in
- 8.9.3
- Check
composer show tinymce/tinymce
tinymce
- Ecosystem
- npm
- Affected
- = 7.9.3
- Fixed in
- 7.9.4
- Check
npm ls tinymce
TinyMCE
- Ecosystem
- NuGet
- Affected
- = 7.9.3
- Fixed in
- 7.9.4
- Check
dotnet list package --include-transitive
tinymce/tinymce
- Ecosystem
- Composer (PHP)
- Affected
- = 7.9.3
- Fixed in
- 7.9.4
- Check
composer show tinymce/tinymce
How to fix it
Upgrade to TinyMCE 8.9.3 or later on the 8.x line, or to 7.9.4 or later on the 7.x line:
npm install [email protected]The advisory says there is no official workaround. Because the media plugin is the trigger, removing it from the plugins list is a stopgap, but the advisory does not endorse it. Also sanitize stored HTML on the server before rendering it to other users.
How to tell if you were hit
Search stored editor content for data-mce-object attributes combined with on* event handlers such as onerror or onload, or with script, iframe or embed elements. Check your database fields that hold rich text, and review content edited by lower-privileged users shortly before an administrator opened it. Watch browser-side CSP violation reports for inline script on editor pages.
Original advisory
From the GitHub Advisory Database (CC BY 4.0).
Impact
Stored XSS vulnerability in the media plugin. Attackers can inject malicious scripts via elements crafted through the data-mce-object attribute, which are created and executed before sanitization. Impacts users of TinyMCE with the media plugin enabled.
Patches
This vulnerability has been patched in TinyMCE 8.9.3 and TinyMCE 7.9.4 by ensuring that, when using the media plugin, any content created through the data-mce-object attribute is properly sanitized first.
Workarounds
No official workaround available.
Fix
To avoid this vulnerability:
Upgrade to TinyMCE 8.9.3 or higher. Upgrade to TinyMCE 7.9.4 or higher.
Acknowledgements
Tiny thanks Fariskhi Vidyan and David Vieira Kurz (HiSolutions AG) for their help identifying this vulnerability.
Credited to farisv, secalert.
Questions
- Which TinyMCE versions fix CVE-2026-116675?
8.9.3 for the 8.x line and 7.9.4 for the 7.x line. Affected: 8.5.1 up to 8.9.3, and 7.9.3.
- Am I safe if I do not use the media plugin?
The advisory says it impacts users of TinyMCE with the media plugin enabled. If it is not loaded, this flaw does not apply to you.
- Is there a workaround?
The advisory states no official workaround is available. Upgrade.
- Does it need user interaction?
Yes. It is stored XSS, so a victim has to open or edit the poisoned content. The CVSS vector marks passive user interaction and low privileges for the attacker.
References
How this page is made: the data panel comes from the GitHub Advisory Database, CISA’s KEV catalog, the NVD and FIRST EPSS, and updates twice a day. The analysis is written by an AI model from the sources listed above and checked by automated rules before it is published. Check versions against the vendor's advisory before you act. Methodology
More npm vulnerabilities
All npm entriesCVE-2026-47759
TinyMCE Cross-Site Scripting (XSS) vulnerability using through data-mce- prefixed src, href, style attributes
high8.7No fixJun 5, 2026CVE-2026-47760
TinyMCE Cross-Site Scripting (XSS) vulnerability using sanitization bypass through nested SVGs
high8.7Jun 5, 2026CVE-2026-47761
TinyMCE Cross-Site Scripting (XSS) vulnerability using media plugin `data-mce-object` injection
high8.7No fixJun 5, 2026CVE-2026-47762
TinyMCE Cross-Site Scripting (XSS) vulnerability through `mce:protected` comments
high8.7No fixJun 5, 2026CVE-2024-38356
TinyMCE Cross-Site Scripting (XSS) vulnerability using noneditable_regexp option
medium6.1Jun 19, 2024CVE-2024-38357
TinyMCE Cross-Site Scripting (XSS) vulnerability using noscript elements
medium6.1Jun 19, 2024
