p PatchFirst

PatchFirst · Aktuelle Sicherheitslücken

Sicherheitslücken in solspace/craft-freeform

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

Sicherheitslücken filtern
Filter zurücksetzen

Sicherheitslücken: 6

  1. CVE-2026-73858

    Mittel · CVSS 5.3EPSS 0,55%Öffentlicher ExploitKorrektur verfügbar

    Solspace Freeform: Limited Twig template injection via submitted field values

    Solspace Freeform plugin for Craft CMS 5.x is a super flexible form-building tool. From 5.0.0 through 5.10.13, submitted values from public Freeform forms can be evaluated by the isolated Twig renderer when rendered into HTML attributes. An unauthenticated attacker can place Twig expressions in submitted field values, including value attributes, and receive evaluated PHP, operating-system, or Craft filesystem-path constants in the form response. The isolated context was not shown to expose Craft globals, environment variables, credentials, arbitrary files, or code execution, so the confirmed impact is limited server and environment informatio

    • Auf 5.10.14 aktualisieren
    Veröffentlicht Aktualisiert
  2. CVE-2026-26188

    Mittel · CVSS 5.1EPSS 0,3%Korrektur verfügbar

    Solspace Freeform plugin affected by Stored Cross-Site Scripting (XSS) in Freeform Craft Plugin CP UI (builder/integrations)

    Solspace Freeform plugin for Craft CMS 5.x is a super flexible form-building tool. An authenticated, low-privilege user (able to create/edit forms) can inject arbitrary HTML/JS into the Craft Control Panel (CP) builder and integrations views. User-controlled form labels and integration metadata are rendered with dangerouslySetInnerHTML without sanitization, leading to stored XSS that executes when any admin views the builder/integration screens. This vulnerability is fixed in 5.14.7.

    • Auf 5.14.7 aktualisieren
    Veröffentlicht Aktualisiert
  3. GHSA-rwr8-xrpw-9qf5

    Nicht bewertetKorrektur verfügbar

    solspace/craft-freeform Exposed to Known Axios Vulnerabilities via Precompiled Assets

    ### Summary The latest versions of both 4.x and 5.x are using Axios versions < 1.7.5 and as such are subject to known vulnerabilities as per: https://security.snyk.io/package/npm/axios ### Details We've had this flagged up in a pen test, which indicates the issue stems from this script: /freeform/plugin.js. I couldn't see any reference to vulnerable axios versions in your package.json files, but noticed some precompiled files in packages/plugin so I'm assuming those are where the issue lies.

    • Auf 4.1.22 aktualisieren
    • Auf 5.5.9 aktualisieren
    Veröffentlicht Aktualisiert
  4. GHSA-44jg-mv3h-wj6g

    Mittel · CVSS 4.8Korrektur verfügbar

    solspace/craft-freeform Vulnerable to XSS in `PhpSpreadsheet` HTML Writer Due to Unsanitized Styling Data

    ### Summary _Short summary of the problem. Make the impact and severity as clear as possible. For example: An unsafe deserialization vulnerability allows any unauthenticated user to execute arbitrary code on the server._ \PhpOffice\PhpSpreadsheet\Writer\Html doesn't sanitize spreadsheet styling information such as font names, allowing an attacker to inject arbitrary JavaScript on the page. ### Details _Give all details on the vulnerability. Pointing to the incriminated source code is very helpful for the maintainer._ See https://github.com/advisories/GHSA-wgmf-q9vr-vww6 ### PoC _Complete instructions, including specific configuration deta

    • Auf 4.1.23 aktualisieren
    Veröffentlicht Aktualisiert
  5. GHSA-58q2-9x27-h2jm

    Mittel · CVSS 6.9Korrektur verfügbar

    solspace/craft-freeform Has a DoS Vulnerability

    ### Summary Freeform plugin v4.1.29 uses vulnerable Axios ^1.7.7 allowing unauthenticated attackers to crash servers via malicious data: URIs causing memory exhaustion (CVE-2025-58754). Freeform version: 4.1.29 Craft CMS version: 4.16.8 ### Impact When Axios runs on Node.js and is given a URL with the `data:` scheme, it does not perform HTTP. Instead, its Node http adapter decodes the entire payload into memory (`Buffer`/`Blob`) and returns a synthetic 200 response. This path ignores `maxContentLength` / `maxBodyLength` (which only protect HTTP responses), so an attacker can supply a very large `data:` URI and cause the process to allocate

    • Auf 4.1.30 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 →