p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in @sveltia/cms

In den letzten 30 Tagen veröffentlichte Sicherheitslücken für @sveltia/cms: 0. Davon im KEV-Katalog: 0.

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 2

  1. GHSA-h5jc-78hr-3pc9

    Mittel · CVSS 4.8Korrektur verfügbar

    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 ac

    • Auf 0.167.3 aktualisieren
    Veröffentlicht Aktualisiert
  2. GHSA-97r8-rf7q-wmjw

    Niedrig · CVSS 2.3Korrektur verfügbar

    Sveltia CMS: Stored XSS in entry summary rendering via entity-decoded HTML

    ### Impact A stored cross-site scripting (XSS) vulnerability affected entry summary rendering in Sveltia CMS. Entry summaries that allowed limited Markdown were parsed, sanitized, and then HTML entities were decoded. This order allowed specially crafted entity-encoded HTML, such as encoded tags or event handler attributes, to become active HTML after sanitization. When the resulting summary was rendered in the CMS UI, arbitrary JavaScript could execute in the browser of a user viewing the affected entry list or search result. The practical impact is limited in currently supported Sveltia CMS usage because the CMS is intended for a single d

    • Auf 0.160.1 aktualisieren
    Veröffentlicht Aktualisiert

Prüfen Sie Ihren Server

Gleichen Sie Ihren installierten Stack und seine Versionen mit den aktuellen Sicherheitsmeldungen ab.

Prüfen Sie Ihren Server →