GHSA-h5jc-78hr-3pc9
Sveltia CMS: Stored XSS in Markdown/RichText preview via unsandboxed same-origin iframe
Impact
A stored cross-site scripting (XSS) vulnerability affected the Markdown/RichText field preview renderer in Sveltia CMS.
The DOMPurify sanitization configuration used for Markdown previews explicitly permitted iframe elements without enforcing a sandbox attribute or restricting iframe sources. Sanitized Markdown output was then inserted into the CMS preview DOM as raw HTML. Because no sandboxing or source validation was applied, a Markdown field containing an iframe whose src pointed to a same-origin uploaded or publicly accessible HTML asset would render an unsandboxed iframe. JavaScript in the framed document could then access the parent CMS window via the browser’s same-origin policy, allowing it to read and write the parent window’s state, DOM, and browser storage, and to trigger actions in the CMS context.
The practical impact is limited in currently supported Sveltia CMS usage because the CMS is intended for a single developer or a small trusted team, and open authoring / untrusted multi-user authoring is not currently implemented. Exploitation requires the ability to place malicious content into the repository or content source that the CMS loads.
Patches
The issue has been patched by replacing the direct DOMPurify call in the Markdown preview renderer with a two-pass sanitization pipeline:
- DOMPurify processes the raw HTML as before.
- A post-processing step validates every
iframeelement in the sanitized output. Any iframe whose src does not use anhttps://URL, uses a same-origin URL, uses a relative path, or uses any other non-HTTPS scheme (javascript:,data:,blob:, , etc.) is removed from the output. Surviving iframes (HTTPS cross-origin only) have asandboxattribute enforced with at minimumallow-scripts allow-same-origin, which confines the framed document to its own origin and prevents it from accessing the parent CMS window.
Users should upgrade to Sveltia CMS v0.167.3 or later.
Workarounds
If upgrading is not immediately possible, avoid loading CMS content from untrusted authors and review Markdown field content for iframe elements pointing to same-origin or relative paths.
Administrators can also reduce exposure by limiting repository or content source write access to trusted users only.
References
Attack profile
How easy it is to exploit
- Attack vector
- Network
- Complexity
- Low
- Privileges needed
- Low
- User interaction
- Active
What an attacker can affect
- Confidentiality
- None
- Integrity
- None
- Availability
- None
What each source reports
GitHub Advisories Score used
Sveltia CMS: Stored XSS in Markdown/RichText preview via unsandboxed same-origin iframe
Impact
A stored cross-site scripting (XSS) vulnerability affected the Markdown/RichText field preview renderer in Sveltia CMS.
The DOMPurify sanitization configuration used for Markdown previews explicitly permitted iframe elements without enforcing a sandbox attribute or restricting iframe sources. Sanitized Markdown output was then inserted into the CMS preview DOM as raw HTML. Because no sandboxing or source validation was applied, a Markdown field containing an iframe whose src pointed to a same-origin uploaded or publicly accessible HTML asset would render an unsandboxed iframe. JavaScript in the framed document could then access the parent CMS window via the browser’s same-origin policy, allowing it to read and write the parent window’s state, DOM, and browser storage, and to trigger actions in the CMS context.
The practical impact is limited in currently supported Sveltia CMS usage because the CMS is intended for a single developer or a small trusted team, and open authoring / untrusted multi-user authoring is not currently implemented. Exploitation requires the ability to place malicious content into the repository or content source that the CMS loads.
Patches
The issue has been patched by replacing the direct DOMPurify call in the Markdown preview renderer with a two-pass sanitization pipeline:
- DOMPurify processes the raw HTML as before.
- A post-processing step validates every
iframeelement in the sanitized output. Any iframe whose src does not use anhttps://URL, uses a same-origin URL, uses a relative path, or uses any other non-HTTPS scheme (javascript:,data:,blob:, , etc.) is removed from the output. Surviving iframes (HTTPS cross-origin only) have asandboxattribute enforced with at minimumallow-scripts allow-same-origin, which confines the framed document to its own origin and prevents it from accessing the parent CMS window.
Users should upgrade to Sveltia CMS v0.167.3 or later.
Workarounds
If upgrading is not immediately possible, avoid loading CMS content from untrusted authors and review Markdown field content for iframe elements pointing to same-origin or relative paths.
Administrators can also reduce exposure by limiting repository or content source write access to trusted users only.
References
- Record
GHSA-h5jc-78hr-3pc9- CVSS 4.0
- 1.1 Low
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:U - Weakness
- CWE-79
- Updated
- 2026-11-02
OSV
Sveltia CMS: Stored XSS in Markdown/RichText preview via unsandboxed same-origin iframe
Impact
A stored cross-site scripting (XSS) vulnerability affected the Markdown/RichText field preview renderer in Sveltia CMS.
The DOMPurify sanitization configuration used for Markdown previews explicitly permitted iframe elements without enforcing a sandbox attribute or restricting iframe sources. Sanitized Markdown output was then inserted into the CMS preview DOM as raw HTML. Because no sandboxing or source validation was applied, a Markdown field containing an iframe whose src pointed to a same-origin uploaded or publicly accessible HTML asset would render an unsandboxed iframe. JavaScript in the framed document could then access the parent CMS window via the browser’s same-origin policy, allowing it to read and write the parent window’s state, DOM, and browser storage, and to trigger actions in the CMS context.
The practical impact is limited in currently supported Sveltia CMS usage because the CMS is intended for a single developer or a small trusted team, and open authoring / untrusted multi-user authoring is not currently implemented. Exploitation requires the ability to place malicious content into the repository or content source that the CMS loads.
Patches
The issue has been patched by replacing the direct DOMPurify call in the Markdown preview renderer with a two-pass sanitization pipeline:
- DOMPurify processes the raw HTML as before.
- A post-processing step validates every
iframeelement in the sanitized output. Any iframe whose src does not use anhttps://URL, uses a same-origin URL, uses a relative path, or uses any other non-HTTPS scheme (javascript:,data:,blob:, , etc.) is removed from the output. Surviving iframes (HTTPS cross-origin only) have asandboxattribute enforced with at minimumallow-scripts allow-same-origin, which confines the framed document to its own origin and prevents it from accessing the parent CMS window.
Users should upgrade to Sveltia CMS v0.167.3 or later.
Workarounds
If upgrading is not immediately possible, avoid loading CMS content from untrusted authors and review Markdown field content for iframe elements pointing to same-origin or relative paths.
Administrators can also reduce exposure by limiting repository or content source write access to trusted users only.
References
- Record
GHSA-h5jc-78hr-3pc9- CVSS 4.0
- 1.1 Low
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N/E:U - Weakness
- CWE-79
- Updated
- 2026-11-02
Affected packages
| Package | Affected | Fixed |
|---|---|---|
@sveltia/cmsnpm | before 0.167.3 | 0.167.3 |
History
| Recorded | Changed | Sources |
|---|---|---|
| first indexed | GitHub Advisories, OSV |
Dates are when Every CVE recorded each change. Upstream dates may differ.
In short
GHSA-h5jc-78hr-3pc9 is a low vulnerability (CVSS 1.1) in @sveltia/cms, published June 19, 2026. No source lists public exploit code. Fixed in @sveltia/cms 0.167.3.