<?xml version='1.0' encoding='UTF-8'?>
<?xml-stylesheet href="/static/style.xsl" type="text/xsl"?>
<rss xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/" version="2.0">
  <channel>
    <title>Most recent entries from all</title>
    <link>https://cve.radiocsirt.org</link>
    <description>Contains only the most 10 recent entries.</description>
    <docs>http://www.rssboard.org/rss-specification</docs>
    <generator>python-feedgen</generator>
    <language>en</language>
    <lastBuildDate>Tue, 06 Oct 2026 09:18:23 +0000</lastBuildDate>
    <item>
      <title>EUVD-2026-322224</title>
      <link>https://cve.radiocsirt.org/vuln/euvd-2026-322224</link>
      <description>EUVD-2026-322224</description>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/euvd-2026-322224</guid>
    </item>
    <item>
      <title>fkie_cve-2026-45089</title>
      <link>https://cve.radiocsirt.org/vuln/fkie_cve-2026-45089</link>
      <description>&lt;p&gt;Dalfox is a powerful open-source XSS scanner and utility focused on automation. Prior to 2.13.0, 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&amp;#39;s request body, then propagated unchanged through dalfox.Initialize into the scan engine&amp;#39;s logging path. The logger opens the attacker-supplied path with os.O_APPEND|os.O_CREATE|os.O_WRONLY 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. This vulnerability is fixed in 2.13.0.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Dalfox is a powerful open-source XSS scanner and utility focused on automation. Prior to 2.13.0, 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&amp;#39;s request body, then propagated unchanged through dalfox.Initialize into the scan engine&amp;#39;s logging path. The logger opens the attacker-supplied path with os.O_APPEND|os.O_CREATE|os.O_WRONLY 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. This vulnerability is fixed in 2.13.0.&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/fkie_cve-2026-45089</guid>
    </item>
    <item>
      <title>GHSA-8hf9-3q64-q2qf — Dalfox Server Mode has an Unauthenticated Arbitrary File Create/Append via `output` Option</title>
      <link>https://cve.radiocsirt.org/vuln/ghsa-8hf9-3q64-q2qf</link>
      <description>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/hahwul/dalfox/v2&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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&amp;#39;s request body, then propagated unchanged through `dalfox.Initialize` into the scan engine&amp;#39;s logging path. The logger opens the attacker-supplied path with `os.O_APPEND|os.O_CREATE|os.O_WRONLY` 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.&lt;/p&gt;
&lt;p&gt;## Severity&lt;/p&gt;
&lt;p&gt;**High** (CVSS 3.1: 8.2)&lt;/p&gt;
&lt;p&gt;`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L`&lt;/p&gt;
&lt;p&gt;- **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 attacker-supplied in the JSON body.
- **Privileges Required:** None — `--api-key` defaults to `&amp;#34;&amp;#34;`, so the auth middleware is never registered.
- **User Interaction:** None.
- **Scope:** Unchanged — the file write stays within the dalfox process&amp;#39;s OS authority.
- **Confidentiality Impact:** None — this is a write-only primitive; no data is returned to the caller.
- **Integrity Impact:** High — the attacker has full control over which file path is opened…&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;&lt;strong&gt;Affected:&lt;/strong&gt; Go: github.com/hahwul/dalfox/v2&lt;/p&gt;
&lt;p&gt;## Summary&lt;/p&gt;
&lt;p&gt;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&amp;#39;s request body, then propagated unchanged through `dalfox.Initialize` into the scan engine&amp;#39;s logging path. The logger opens the attacker-supplied path with `os.O_APPEND|os.O_CREATE|os.O_WRONLY` 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.&lt;/p&gt;
&lt;p&gt;## Severity&lt;/p&gt;
&lt;p&gt;**High** (CVSS 3.1: 8.2)&lt;/p&gt;
&lt;p&gt;`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:L`&lt;/p&gt;
&lt;p&gt;- **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 attacker-supplied in the JSON body.
- **Privileges Required:** None — `--api-key` defaults to `&amp;#34;&amp;#34;`, so the auth middleware is never registered.
- **User Interaction:** None.
- **Scope:** Unchanged — the file write stays within the dalfox process&amp;#39;s OS authority.
- **Confidentiality Impact:** None — this is a write-only primitive; no data is returned to the caller.
- **Integrity Impact:** High — the attacker has full control over which file path is opened…&lt;/p&gt;</content:encoded>
      <guid isPermaLink="false">https://cve.radiocsirt.org/vuln/ghsa-8hf9-3q64-q2qf</guid>
    </item>
  </channel>
</rss>
