p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in spip

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 17

  1. CVE-2026-8430

    Kritisch · CVSS 9.2EPSS 0,43%Keine Korrektur veröffentlicht

    SPIP < 4.4.14 Remote Code Execution via nginx

    SPIP versions prior to 4.4.14 contain a remote code execution vulnerability in the public space that is limited to certain nginx configurations, allowing attackers to execute arbitrary code in the context of the web server. Attackers can exploit this vulnerability through specific nginx configuration scenarios to achieve code execution, and this issue is not mitigated by the SPIP security screen.

    Veröffentlicht Aktualisiert
  2. CVE-2026-8429

    Hoch · CVSS 8.7EPSS 0,5%Keine Korrektur veröffentlicht

    SPIP < 4.4.14 Remote Code Execution via Private Space

    SPIP versions prior to 4.4.14 contain a remote code execution vulnerability in the private space that allows attackers to execute arbitrary code in the context of the web server. Attackers can exploit this vulnerability to achieve code execution that bypasses the SPIP security screen protections.

    Veröffentlicht Aktualisiert
  3. CVE-2026-22205

    Hoch · CVSS 8.7EPSS 0,53%Keine Korrektur veröffentlicht

    SPIP < 4.4.10 Authentication Bypass via PHP Type Juggling

    SPIP versions prior to 4.4.10 contain an authentication bypass vulnerability caused by PHP type juggling that allows unauthenticated attackers to access protected information. Attackers can exploit loose type comparisons in authentication logic to bypass login verification and retrieve sensitive internal data.

    Veröffentlicht Aktualisiert
  4. CVE-2026-22206

    Hoch · CVSS 8.7EPSS 0,64%Keine Korrektur veröffentlicht

    SPIP < 4.4.10 SQL Injection RCE via Union & PHP Tags

    SPIP versions prior to 4.4.10 contain a SQL injection vulnerability that allows authenticated low-privilege users to execute arbitrary SQL queries by manipulating union-based injection techniques. Attackers can exploit this SQL injection flaw combined with PHP tag processing to achieve remote code execution on the server.

    Veröffentlicht Aktualisiert
  5. CVE-2026-27475

    Kritisch · CVSS 9.2EPSS 0,91%Keine Korrektur veröffentlicht

    SPIP < 4.4.9 Insecure Deserialization

    SPIP before 4.4.9 allows Insecure Deserialization in the public area through the table_valeur filter and the DATA iterator, which accept serialized data. An attacker who can place malicious serialized content (a pre-condition requiring prior access or another vulnerability) can trigger arbitrary object instantiation and potentially achieve code execution. The use of serialized data in these components has been deprecated and will be removed in SPIP 5. This vulnerability is not mitigated by the SPIP security screen.

    Veröffentlicht Aktualisiert
  6. CVE-2026-27474

    Mittel · CVSS 4.8EPSS 0,29%Keine Korrektur veröffentlicht

    SPIP < 4.4.9 Cross-Site Scripting in Private Area (Incomplete Fix)

    SPIP before 4.4.9 allows Cross-Site Scripting (XSS) in the private area, complementing an incomplete fix from SPIP 4.4.8. The echappe_anti_xss() function was not systematically applied to input, form, button, and anchor (a) HTML tags, allowing an attacker to inject malicious scripts through these elements. This vulnerability is not mitigated by the SPIP security screen.

    Veröffentlicht Aktualisiert
  7. CVE-2026-27473

    Mittel · CVSS 5.1EPSS 0,3%Keine Korrektur veröffentlicht

    SPIP < 4.4.9 Stored Cross-Site Scripting via Syndicated Sites

    SPIP before 4.4.9 allows Stored Cross-Site Scripting (XSS) via syndicated sites in the private area. The #URL_SYNDIC output is not properly sanitized on the private syndicated site page, allowing an attacker who can set a malicious syndication URL to inject persistent scripts that execute when other administrators view the syndicated site details.

    Veröffentlicht Aktualisiert
  8. CVE-2026-27472

    Mittel · CVSS 5.3EPSS 0,31%Keine Korrektur veröffentlicht

    SPIP < 4.4.9 Blind Server-Side Request Forgery via Syndicated Sites

    SPIP before 4.4.9 allows Blind Server-Side Request Forgery (SSRF) via syndicated sites in the private area. When editing a syndicated site, the application does not verify that the syndication URL is a valid remote URL, allowing an authenticated attacker to make the server issue requests to arbitrary internal or external destinations. This vulnerability is not mitigated by the SPIP security screen.

    Veröffentlicht Aktualisiert
  9. CVE-2026-26223

    Mittel · CVSS 5.1EPSS 0,21%Keine Korrektur veröffentlicht

    SPIP < 4.4.8 Cross-Site Scripting via Iframe Tags in Private Area

    SPIP before 4.4.8 allows cross-site scripting (XSS) in the private area via malicious iframe tags. The application does not properly sandbox or escape iframe content in the back-office, allowing an attacker to inject and execute malicious scripts. The fix adds a sandbox attribute to iframe tags in the private area. This vulnerability is not mitigated by the SPIP security screen.

    Veröffentlicht Aktualisiert
  10. CVE-2026-26345

    Hoch · CVSS 8.6EPSS 0,21%Keine Korrektur veröffentlicht

    SPIP < 4.4.8 Cross-Site Scripting in Public Area

    SPIP before 4.4.8 contains a stored cross-site scripting (XSS) vulnerability in the public area triggered in certain edge-case usage patterns. The echapper_html_suspect() function does not adequately sanitize user-controlled content, allowing authenticated users with content-editing privileges (e.g., author-level roles and above) to inject malicious scripts. The injected payload may be rendered across multiple pages within the framework and execute in the browser context of other users, including administrators. Successful exploitation can allow attackers to perform actions in the security context of the victim user, including unauthorized mo

    Veröffentlicht Aktualisiert
  11. CVE-2025-71244

    Mittel · CVSS 5.1EPSS 0,21%Keine Korrektur veröffentlicht

    SPIP < 4.4.5 Open Redirect via Login Form

    SPIP before 4.4.5 and 4.3.9 allows an Open Redirect via the login form when used in AJAX mode. An attacker can craft a malicious URL that, when visited by a victim, redirects them to an arbitrary external site after login. This vulnerability only affects sites where the login page has been overridden to function in AJAX mode. It is not mitigated by the SPIP security screen.

    Veröffentlicht Aktualisiert
  12. CVE-2023-53900

    Mittel · CVSS 4.8EPSS 0,32%Keine Korrektur veröffentlicht

    Spip 4.1.10 Admin Account Spoofing via Malicious SVG Upload

    Spip 4.1.10 contains a file upload vulnerability that allows attackers to upload malicious SVG files with embedded external links. Attackers can trick administrators into clicking a crafted SVG logo that redirects to a potentially dangerous URL through improper file upload filtering.

    Veröffentlicht Aktualisiert
  13. CVE-2024-53620

    Mittel · CVSS 4.8EPSS 0,37%Keine Korrektur veröffentlicht

    CVE-2024-53620

    A cross-site scripting (XSS) vulnerability in the Article module of SPIP v4.3.3 allows authenticated attackers to execute arbitrary web scripts or HTML via injecting a crafted payload into the Title parameter.

    Veröffentlicht Aktualisiert
  14. CVE-2024-53619

    Mittel · CVSS 6.3EPSS 0,57%Keine Korrektur veröffentlicht

    CVE-2024-53619

    An authenticated arbitrary file upload vulnerability in the Documents module of SPIP v4.3.3 allows attackers to execute arbitrary code via uploading a crafted PDF file.

    Veröffentlicht Aktualisiert
  15. CVE-2022-23638

    Mittel · CVSS 6.2EPSS 0,68%Keine Korrektur veröffentlicht

    Cross-site Scripting in svg-sanitizer

    svg-sanitizer is a SVG/XML sanitizer written in PHP. A cross-site scripting vulnerability impacts all users of the `svg-sanitizer` library prior to version 0.15.0. This issue is fixed in version 0.15.0. There is currently no workaround available.

    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 →