Skip to content

← Public intelligence

Go package

github.com/hahwul/dalfox/v2

Open actionable advisories and recorded vendor fixes. This public package view has no inventory attached and cannot establish whether your deployment is affected. A vendor fix never resolves your finding; verify your installed version and the source guidance.

Open advisories

3 actionable advisories, newest first. Withdrawn advisories and news are excluded. Coverage is partial.

  1. High, CVSS 8.2GoPublished

    Dalfox Server Mode has an Unauthenticated Arbitrary File Create/Append via output Option

    CVE-2026-45089 · GHSA-8hf9-3q64-q2qf

    Affected
    • Go github.com/hahwul/dalfox/v2 <= 2.12.0
    Fixed in
    2.13.0· Vendor fix available
    Issue
    When dalfox is run in REST API server mode, the output, output-all, and debug fields in model.Options are JSON-tagged and deserialized directly from the attacker's request body, then propagated unchanged through dalfox.Initialize into the scan engine's logging path. The logger opens the attacker-supplied path with os.OAPPEND|os.OCREATE|os.OWRONLY and writes scan log lines to it. Critically, this file write block lives outside the IsLibrary guard in DalLog, so it executes even in server/library mode where file output was never intended to operate. Because no API key is required in the default configuration, an unauthenticated network caller can create or append to any file writable by the dalfox process on the host filesystem. Severity High (CVSS 3.1: 8.2) CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L - Attack Vector: Network — server binds to 0.0.0.0:6664 by default. - Attack Complexity: Low — no preconditions; all trigger options (output, output-all, debug) are fully…

    Recommended action: Upgrade to 2.13.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  2. High, CVSS 7.5GoPublished

    Dalfox Server Mode has an Unauthenticated Arbitrary File Read with Out-of-Band Exfiltration via custom-payload-file

    CVE-2026-45088 · GHSA-35wr-x7v6-9fv2

    Affected
    • Go github.com/hahwul/dalfox/v2 <= 2.12.0
    Fixed in
    2.13.0· Vendor fix available
    Issue
    When dalfox is run in REST API server mode, the custom-payload-file field in model.Options is JSON-tagged and deserialized directly from the attacker's request body, then propagated unchanged through dalfox.Initialize into the scan engine. The engine passes the value to voltFile.ReadLinesOrLiteral, which reads lines from any file path accessible to the dalfox process and embeds each line as an XSS payload in outbound HTTP requests directed at the attacker-controlled target URL. Because the server has no API key by default, an unauthenticated network attacker can exfiltrate the contents of arbitrary files on the dalfox host by reading them line-by-line through scan traffic. Severity High (CVSS 3.1: 7.5) CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N - Attack Vector: Network — server binds to 0.0.0.0:6664 by default; reachable by any network peer. - Attack Complexity: Low — no preconditions beyond network access; skip-discovery and param are both attacker-supplied, so the code…

    Recommended action: Upgrade to 2.13.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →
  3. Critical, CVSS 10.0GoPublished

    Dalfox Server Mode Vulnerable to Unauthenticated Remote Code Execution via found-action

    CVE-2026-45087 · GHSA-v25v-m36w-jp4h

    Affected
    • Go github.com/hahwul/dalfox/v2 <= 2.12.0
    Fixed in
    2.13.0· Vendor fix available
    Issue
    GHSA: Unauthenticated Remote Code Execution via found-action in Dalfox Server Mode Summary When dalfox is started in REST API server mode (dalfox server), the server binds to 0.0.0.0:6664 by default and requires no API key unless the operator explicitly passes --api-key. Because model.Options — including FoundAction and FoundActionShell — is deserialized directly from attacker-supplied JSON in POST /scan, and because dalfox.Initialize explicitly propagates those two fields into the final scan options without stripping them, any unauthenticated caller who can reach the server port can supply an arbitrary shell command that the dalfox process will execute on the host whenever a scan finding is triggered. Severity Critical (CVSS 3.1: 10.0) CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H - Attack Vector: Network — the server binds to 0.0.0.0 by default; reachable by any network peer. - Attack Complexity: Low — the attacker fully controls the scanned URL and can trivially host a one-line…

    Recommended action: Upgrade to 2.13.0 or later, then redeploy and verify.A vendor fix does not resolve your finding until you verify it in your own systems.

    Sources:github.comSource checked Evidence →