{"items":[{"id":"NVI-00003540","kind":"vulnerability","title":"TinyMCE Cross-Site Scripting (XSS) vulnerability in handling iframes","revision":4,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected.","NVD lastModified does not establish freshness of every associated CPE record."],"lifecycle":"active","identifiers":["GHSA-438c-3975-5x3f","CVE-2024-29203"],"plain_summary":"OSV carries this publisher advisory for tinymce, TinyMCE, tinymce/tinymce. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 6.8.1 for tinymce. Confirm the publisher’s latest guidance.","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.8.1 for tinymce/tinymce. Confirm the publisher’s latest guidance.","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-157ab225b5b349e108e5097e42963dea"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"CVSS","as_of":"2026-06-17T07:22:37.320Z","value":"4.3 MEDIUM (3.1)","meaning":"security-advisories@github.com severity; no combined Null risk score.","source_id":"sr-c017aa0ed91b91353b1582d8bda677de"},{"kind":"CVSS","as_of":"2026-06-17T07:22:37.320Z","value":"6.1 MEDIUM (3.1)","meaning":"nvd@nist.gov severity; no combined Null risk score.","source_id":"sr-c017aa0ed91b91353b1582d8bda677de"},{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.713%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.53639. Missing scores are unknown.","source_id":"sr-157ab225b5b349e108e5097e42963dea"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-422faad28b812b1474f5490f404958e6","url":"https://github.com/advisories/GHSA-438c-3975-5x3f","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-438c-3975-5x3f","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.663Z"},{"id":"sr-c017aa0ed91b91353b1582d8bda677de","url":"https://nvd.nist.gov/vuln/detail/CVE-2024-29203","basis":"official_catalog","notes":"This product uses data from the NVD API but is not endorsed or certified by the NVD.","title":"CVE-2024-29203","publisher":"NIST National Vulnerability Database","observed_at":"2026-11-01T00:59:21.595Z"},{"id":"sr-157ab225b5b349e108e5097e42963dea","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2024-29203","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:27:48.610Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"technology":"tinymce","known_exclusions":[],"conditions_summary":"### Impact\nA cross-site scripting (XSS) vulnerability was discovered in TinyMCE’s content insertion code.  This allowed `iframe` elements containing malicious code to execute when inserted into the editor.  These `iframe` elements are restricted in their permissions by same-origin browser protections, but could still trigger operations such as downloading of malicious assets.\n\n### Fix\nTinyMCE 6.8.1 introduced a new `sandbox_iframes` boolean option which adds the `sandbox=\"\"` attribute to every `iframe` element by default when enabled. This will prevent cross-origin, and in special cases same-origin, XSS by embedded resources in `iframe` elements. From TinyMCE 7.0.0 onwards the default value of this option is `true`.\n\nIn TinyMCE 7.0.0 a new `sandbox_iframes_exclusions` option was also added, allowing a list of domains to be specified that should be excluded from having the `sandbox=\"\"` attribute applied when the `sandbox_iframes` option is enabled. By default, this option is set to an array of domains that are provided in embed code by popular websites. To sandbox `iframe` elements from every domain, set this option to `[]`.\n\n### Worka","public_affected_ranges":["SEMVER: introduced 0; fixed 6.8.1"]},{"certainty":"source_listed","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"technology":"TinyMCE","known_exclusions":[],"conditions_summary":"### Impact\nA cross-site scripting (XSS) vulnerability was discovered in TinyMCE’s content insertion code.  This allowed `iframe` elements containing malicious code to execute when inserted into the editor.  These `iframe` elements are restricted in their permissions by same-origin browser protections, but could still trigger operations such as downloading of malicious assets.\n\n### Fix\nTinyMCE 6.8.1 introduced a new `sandbox_iframes` boolean option which adds the `sandbox=\"\"` attribute to every `iframe` element by default when enabled. This will prevent cross-origin, and in special cases same-origin, XSS by embedded resources in `iframe` elements. From TinyMCE 7.0.0 onwards the default value of this option is `true`.\n\nIn TinyMCE 7.0.0 a new `sandbox_iframes_exclusions` option was also added, allowing a list of domains to be specified that should be excluded from having the `sandbox=\"\"` attribute applied when the `sandbox_iframes` option is enabled. By default, this option is set to an array of domains that are provided in embed code by popular websites. To sandbox `iframe` elements from every domain, set this option to `[]`.\n\n### Worka","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.8.1"]},{"certainty":"source_listed","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"technology":"tinymce/tinymce","known_exclusions":[],"conditions_summary":"### Impact\nA cross-site scripting (XSS) vulnerability was discovered in TinyMCE’s content insertion code.  This allowed `iframe` elements containing malicious code to execute when inserted into the editor.  These `iframe` elements are restricted in their permissions by same-origin browser protections, but could still trigger operations such as downloading of malicious assets.\n\n### Fix\nTinyMCE 6.8.1 introduced a new `sandbox_iframes` boolean option which adds the `sandbox=\"\"` attribute to every `iframe` element by default when enabled. This will prevent cross-origin, and in special cases same-origin, XSS by embedded resources in `iframe` elements. From TinyMCE 7.0.0 onwards the default value of this option is `true`.\n\nIn TinyMCE 7.0.0 a new `sandbox_iframes_exclusions` option was also added, allowing a list of domains to be specified that should be excluded from having the `sandbox=\"\"` attribute applied when the `sandbox_iframes` option is enabled. By default, this option is set to an array of domains that are provided in embed code by popular websites. To sandbox `iframe` elements from every domain, set this option to `[]`.\n\n### Worka","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.8.1"]}],"null_published_at":"2026-11-07T22:29:23.381Z","source_updated_at":"2026-09-10T03:50:10.591Z","source_disclosed_at":"2024-03-26T21:23:47.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Source facts changed; compare the preserved prior revision.","null_first_observed_at":"2026-10-31T21:41:49.663Z"},{"id":"NVI-00003540","kind":"vulnerability","title":"TinyMCE Cross-Site Scripting (XSS) vulnerability in handling iframes","revision":3,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-438c-3975-5x3f","CVE-2024-29203"],"plain_summary":"OSV carries this publisher advisory for tinymce, TinyMCE, tinymce/tinymce. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 6.8.1 for tinymce. Confirm the publisher’s latest guidance.","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.8.1 for tinymce/tinymce. Confirm the publisher’s latest guidance.","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-157ab225b5b349e108e5097e42963dea"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-11-01T12:00:16.000Z","value":"0.713%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.53639. Missing scores are unknown.","source_id":"sr-157ab225b5b349e108e5097e42963dea"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-422faad28b812b1474f5490f404958e6","url":"https://github.com/advisories/GHSA-438c-3975-5x3f","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-438c-3975-5x3f","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.663Z"},{"id":"sr-157ab225b5b349e108e5097e42963dea","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2024-29203","publisher":"FIRST EPSS","observed_at":"2026-11-01T14:27:48.610Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"technology":"tinymce","known_exclusions":[],"conditions_summary":"### Impact\nA cross-site scripting (XSS) vulnerability was discovered in TinyMCE’s content insertion code.  This allowed `iframe` elements containing malicious code to execute when inserted into the editor.  These `iframe` elements are restricted in their permissions by same-origin browser protections, but could still trigger operations such as downloading of malicious assets.\n\n### Fix\nTinyMCE 6.8.1 introduced a new `sandbox_iframes` boolean option which adds the `sandbox=\"\"` attribute to every `iframe` element by default when enabled. This will prevent cross-origin, and in special cases same-origin, XSS by embedded resources in `iframe` elements. From TinyMCE 7.0.0 onwards the default value of this option is `true`.\n\nIn TinyMCE 7.0.0 a new `sandbox_iframes_exclusions` option was also added, allowing a list of domains to be specified that should be excluded from having the `sandbox=\"\"` attribute applied when the `sandbox_iframes` option is enabled. By default, this option is set to an array of domains that are provided in embed code by popular websites. To sandbox `iframe` elements from every domain, set this option to `[]`.\n\n### Worka","public_affected_ranges":["SEMVER: introduced 0; fixed 6.8.1"]},{"certainty":"source_listed","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"technology":"TinyMCE","known_exclusions":[],"conditions_summary":"### Impact\nA cross-site scripting (XSS) vulnerability was discovered in TinyMCE’s content insertion code.  This allowed `iframe` elements containing malicious code to execute when inserted into the editor.  These `iframe` elements are restricted in their permissions by same-origin browser protections, but could still trigger operations such as downloading of malicious assets.\n\n### Fix\nTinyMCE 6.8.1 introduced a new `sandbox_iframes` boolean option which adds the `sandbox=\"\"` attribute to every `iframe` element by default when enabled. This will prevent cross-origin, and in special cases same-origin, XSS by embedded resources in `iframe` elements. From TinyMCE 7.0.0 onwards the default value of this option is `true`.\n\nIn TinyMCE 7.0.0 a new `sandbox_iframes_exclusions` option was also added, allowing a list of domains to be specified that should be excluded from having the `sandbox=\"\"` attribute applied when the `sandbox_iframes` option is enabled. By default, this option is set to an array of domains that are provided in embed code by popular websites. To sandbox `iframe` elements from every domain, set this option to `[]`.\n\n### Worka","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.8.1"]},{"certainty":"source_listed","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"technology":"tinymce/tinymce","known_exclusions":[],"conditions_summary":"### Impact\nA cross-site scripting (XSS) vulnerability was discovered in TinyMCE’s content insertion code.  This allowed `iframe` elements containing malicious code to execute when inserted into the editor.  These `iframe` elements are restricted in their permissions by same-origin browser protections, but could still trigger operations such as downloading of malicious assets.\n\n### Fix\nTinyMCE 6.8.1 introduced a new `sandbox_iframes` boolean option which adds the `sandbox=\"\"` attribute to every `iframe` element by default when enabled. This will prevent cross-origin, and in special cases same-origin, XSS by embedded resources in `iframe` elements. From TinyMCE 7.0.0 onwards the default value of this option is `true`.\n\nIn TinyMCE 7.0.0 a new `sandbox_iframes_exclusions` option was also added, allowing a list of domains to be specified that should be excluded from having the `sandbox=\"\"` attribute applied when the `sandbox_iframes` option is enabled. By default, this option is set to an array of domains that are provided in embed code by popular websites. To sandbox `iframe` elements from every domain, set this option to `[]`.\n\n### Worka","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.8.1"]}],"null_published_at":"2026-11-03T17:49:18.499Z","source_updated_at":"2026-09-10T03:50:10.591Z","source_disclosed_at":"2024-03-26T21:23:47.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:41:49.663Z"},{"id":"NVI-00003540","kind":"vulnerability","title":"TinyMCE Cross-Site Scripting (XSS) vulnerability in handling iframes","revision":2,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-438c-3975-5x3f","CVE-2024-29203"],"plain_summary":"OSV carries this publisher advisory for tinymce, TinyMCE, tinymce/tinymce. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 6.8.1 for tinymce. Confirm the publisher’s latest guidance.","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.8.1 for tinymce/tinymce. Confirm the publisher’s latest guidance.","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"Identify the exact component and deployed version, examine the linked publisher’s conditions, and retain evidence of any mitigation.","source_ids":["sr-609378c0737e0cf1ae15a222231f1bed"],"action_type":"investigate","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[{"kind":"EPSS","as_of":"2026-10-31T12:00:27.000Z","value":"0.713%","meaning":"FIRST EPSS model v2026.06.15; exploitation probability over 30 days, percentile 0.5364. Missing scores are unknown.","source_id":"sr-609378c0737e0cf1ae15a222231f1bed"}],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-422faad28b812b1474f5490f404958e6","url":"https://github.com/advisories/GHSA-438c-3975-5x3f","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-438c-3975-5x3f","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.663Z"},{"id":"sr-609378c0737e0cf1ae15a222231f1bed","url":"https://www.first.org/epss/data.html","basis":"official_catalog","notes":"FIRST EPSS; probability of exploitation in the next 30 days, not local compromise. Dataset date/model retained; FIRST services terms apply.","title":"CVE-2024-29203","publisher":"FIRST EPSS","observed_at":"2026-10-31T22:06:03.704Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"technology":"tinymce","known_exclusions":[],"conditions_summary":"### Impact\nA cross-site scripting (XSS) vulnerability was discovered in TinyMCE’s content insertion code.  This allowed `iframe` elements containing malicious code to execute when inserted into the editor.  These `iframe` elements are restricted in their permissions by same-origin browser protections, but could still trigger operations such as downloading of malicious assets.\n\n### Fix\nTinyMCE 6.8.1 introduced a new `sandbox_iframes` boolean option which adds the `sandbox=\"\"` attribute to every `iframe` element by default when enabled. This will prevent cross-origin, and in special cases same-origin, XSS by embedded resources in `iframe` elements. From TinyMCE 7.0.0 onwards the default value of this option is `true`.\n\nIn TinyMCE 7.0.0 a new `sandbox_iframes_exclusions` option was also added, allowing a list of domains to be specified that should be excluded from having the `sandbox=\"\"` attribute applied when the `sandbox_iframes` option is enabled. By default, this option is set to an array of domains that are provided in embed code by popular websites. To sandbox `iframe` elements from every domain, set this option to `[]`.\n\n### Worka","public_affected_ranges":["SEMVER: introduced 0; fixed 6.8.1"]},{"certainty":"source_listed","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"technology":"TinyMCE","known_exclusions":[],"conditions_summary":"### Impact\nA cross-site scripting (XSS) vulnerability was discovered in TinyMCE’s content insertion code.  This allowed `iframe` elements containing malicious code to execute when inserted into the editor.  These `iframe` elements are restricted in their permissions by same-origin browser protections, but could still trigger operations such as downloading of malicious assets.\n\n### Fix\nTinyMCE 6.8.1 introduced a new `sandbox_iframes` boolean option which adds the `sandbox=\"\"` attribute to every `iframe` element by default when enabled. This will prevent cross-origin, and in special cases same-origin, XSS by embedded resources in `iframe` elements. From TinyMCE 7.0.0 onwards the default value of this option is `true`.\n\nIn TinyMCE 7.0.0 a new `sandbox_iframes_exclusions` option was also added, allowing a list of domains to be specified that should be excluded from having the `sandbox=\"\"` attribute applied when the `sandbox_iframes` option is enabled. By default, this option is set to an array of domains that are provided in embed code by popular websites. To sandbox `iframe` elements from every domain, set this option to `[]`.\n\n### Worka","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.8.1"]},{"certainty":"source_listed","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"technology":"tinymce/tinymce","known_exclusions":[],"conditions_summary":"### Impact\nA cross-site scripting (XSS) vulnerability was discovered in TinyMCE’s content insertion code.  This allowed `iframe` elements containing malicious code to execute when inserted into the editor.  These `iframe` elements are restricted in their permissions by same-origin browser protections, but could still trigger operations such as downloading of malicious assets.\n\n### Fix\nTinyMCE 6.8.1 introduced a new `sandbox_iframes` boolean option which adds the `sandbox=\"\"` attribute to every `iframe` element by default when enabled. This will prevent cross-origin, and in special cases same-origin, XSS by embedded resources in `iframe` elements. From TinyMCE 7.0.0 onwards the default value of this option is `true`.\n\nIn TinyMCE 7.0.0 a new `sandbox_iframes_exclusions` option was also added, allowing a list of domains to be specified that should be excluded from having the `sandbox=\"\"` attribute applied when the `sandbox_iframes` option is enabled. By default, this option is set to an array of domains that are provided in embed code by popular websites. To sandbox `iframe` elements from every domain, set this option to `[]`.\n\n### Worka","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.8.1"]}],"null_published_at":"2026-11-01T01:45:38.534Z","source_updated_at":"2026-09-10T03:50:10.591Z","source_disclosed_at":"2024-03-26T21:23:47.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"Dated EPSS estimate updated; this is not a new disclosure or proof of exploitation.","null_first_observed_at":"2026-10-31T21:41:49.663Z"},{"id":"NVI-00003540","kind":"vulnerability","title":"TinyMCE Cross-Site Scripting (XSS) vulnerability in handling iframes","revision":1,"unknowns":["Customer inventory, deployment, reachability and exploitation have not been inspected."],"lifecycle":"active","identifiers":["GHSA-438c-3975-5x3f","CVE-2024-29203"],"plain_summary":"OSV carries this publisher advisory for tinymce, TinyMCE, tinymce/tinymce. This is an aggregated source copy; consult the original publisher and compare update dates.","review_status":"source_listed","control_topics":[],"public_actions":[{"summary":"The original advisory lists fixed boundaries 6.8.1 for tinymce. Confirm the publisher’s latest guidance.","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null},{"summary":"The original advisory lists fixed boundaries 6.8.1 for tinymce/tinymce. Confirm the publisher’s latest guidance.","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"action_type":"vendor_patch","limitations":"Confirm current vendor support, compatibility and deployment evidence. This report has not tested a fix in your system.","current_supported_target":null}],"schema_version":"1.1.0","source_metrics":[],"why_it_matters":"Published affected context helps an owner decide what evidence to gather. This report has not examined your application.","related_sources":[{"id":"sr-422faad28b812b1474f5490f404958e6","url":"https://github.com/advisories/GHSA-438c-3975-5x3f","basis":"vendor_advisory","notes":"GitHub-origin advisory, CC-BY-4.0; OSV is an aggregate copy, not independent corroboration.","title":"GHSA-438c-3975-5x3f","publisher":"GitHub Advisory Database via OSV","observed_at":"2026-10-31T21:41:49.663Z"}],"affected_context":[{"certainty":"source_listed","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"technology":"tinymce","known_exclusions":[],"conditions_summary":"### Impact\nA cross-site scripting (XSS) vulnerability was discovered in TinyMCE’s content insertion code.  This allowed `iframe` elements containing malicious code to execute when inserted into the editor.  These `iframe` elements are restricted in their permissions by same-origin browser protections, but could still trigger operations such as downloading of malicious assets.\n\n### Fix\nTinyMCE 6.8.1 introduced a new `sandbox_iframes` boolean option which adds the `sandbox=\"\"` attribute to every `iframe` element by default when enabled. This will prevent cross-origin, and in special cases same-origin, XSS by embedded resources in `iframe` elements. From TinyMCE 7.0.0 onwards the default value of this option is `true`.\n\nIn TinyMCE 7.0.0 a new `sandbox_iframes_exclusions` option was also added, allowing a list of domains to be specified that should be excluded from having the `sandbox=\"\"` attribute applied when the `sandbox_iframes` option is enabled. By default, this option is set to an array of domains that are provided in embed code by popular websites. To sandbox `iframe` elements from every domain, set this option to `[]`.\n\n### Worka","public_affected_ranges":["SEMVER: introduced 0; fixed 6.8.1"]},{"certainty":"source_listed","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"technology":"TinyMCE","known_exclusions":[],"conditions_summary":"### Impact\nA cross-site scripting (XSS) vulnerability was discovered in TinyMCE’s content insertion code.  This allowed `iframe` elements containing malicious code to execute when inserted into the editor.  These `iframe` elements are restricted in their permissions by same-origin browser protections, but could still trigger operations such as downloading of malicious assets.\n\n### Fix\nTinyMCE 6.8.1 introduced a new `sandbox_iframes` boolean option which adds the `sandbox=\"\"` attribute to every `iframe` element by default when enabled. This will prevent cross-origin, and in special cases same-origin, XSS by embedded resources in `iframe` elements. From TinyMCE 7.0.0 onwards the default value of this option is `true`.\n\nIn TinyMCE 7.0.0 a new `sandbox_iframes_exclusions` option was also added, allowing a list of domains to be specified that should be excluded from having the `sandbox=\"\"` attribute applied when the `sandbox_iframes` option is enabled. By default, this option is set to an array of domains that are provided in embed code by popular websites. To sandbox `iframe` elements from every domain, set this option to `[]`.\n\n### Worka","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.8.1"]},{"certainty":"source_listed","source_ids":["sr-422faad28b812b1474f5490f404958e6"],"technology":"tinymce/tinymce","known_exclusions":[],"conditions_summary":"### Impact\nA cross-site scripting (XSS) vulnerability was discovered in TinyMCE’s content insertion code.  This allowed `iframe` elements containing malicious code to execute when inserted into the editor.  These `iframe` elements are restricted in their permissions by same-origin browser protections, but could still trigger operations such as downloading of malicious assets.\n\n### Fix\nTinyMCE 6.8.1 introduced a new `sandbox_iframes` boolean option which adds the `sandbox=\"\"` attribute to every `iframe` element by default when enabled. This will prevent cross-origin, and in special cases same-origin, XSS by embedded resources in `iframe` elements. From TinyMCE 7.0.0 onwards the default value of this option is `true`.\n\nIn TinyMCE 7.0.0 a new `sandbox_iframes_exclusions` option was also added, allowing a list of domains to be specified that should be excluded from having the `sandbox=\"\"` attribute applied when the `sandbox_iframes` option is enabled. By default, this option is set to an array of domains that are provided in embed code by popular websites. To sandbox `iframe` elements from every domain, set this option to `[]`.\n\n### Worka","public_affected_ranges":["ECOSYSTEM: introduced 0; fixed 6.8.1"]}],"null_published_at":"2026-10-31T22:12:48.020Z","source_updated_at":"2026-09-10T03:50:10.591Z","source_disclosed_at":"2024-03-26T21:23:47.000Z","is_synthetic_fixture":false,"null_last_reviewed_at":null,"public_change_summary":"First indexed by Null; source disclosure date is shown separately.","null_first_observed_at":"2026-10-31T21:41:49.663Z"}],"next_cursor":null,"snapshot_revision":"42594"}