CVE-2026-45088
Received Received - Intake
Stored XSS via Arbitrary File Read in Dalfox Scanner

Publication date: 2026-05-27

Last updated on: 2026-05-27

Assigner: GitHub, Inc.

Description
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 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. This vulnerability is fixed in 2.13.0.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-27
Last Modified
2026-05-27
Generated
2026-05-28
AI Q&A
2026-05-27
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
dalfox dalfox 2.13.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-73 The product allows user input to control or influence paths or file names that are used in filesystem operations.
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.
CWE-552 The product makes files or directories accessible to unauthorized actors, even though they should not be.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in Dalfox, an open-source XSS scanner, when run in REST API server mode prior to version 2.13.0. The issue arises because the custom-payload-file field is deserialized directly from an attacker’s request without validation and passed to a function that reads lines from any file accessible to the Dalfox process. As a result, an unauthenticated attacker can cause Dalfox to read and exfiltrate arbitrary files from the host system by embedding their contents into outbound HTTP requests.


How can this vulnerability impact me? :

This vulnerability allows an unauthenticated network attacker to read and exfiltrate arbitrary files from the Dalfox host system. This can lead to the exposure of sensitive information stored on the host, potentially compromising confidentiality. Since the attacker can access files line-by-line through scan traffic, it poses a significant risk of data leakage.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, upgrade Dalfox to version 2.13.0 or later, where the issue has been fixed.


How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:

This vulnerability allows unauthenticated attackers to read and exfiltrate arbitrary files from the Dalfox host system, leading to a complete confidentiality compromise of sensitive files accessible to the Dalfox process.

Such unauthorized data exposure can result in violations of data protection regulations and standards like GDPR and HIPAA, which mandate strict controls over the confidentiality and integrity of sensitive personal and health information.

Therefore, if Dalfox is used in environments subject to these regulations, exploitation of this vulnerability could lead to non-compliance due to unauthorized disclosure of protected data.


How can this vulnerability be detected on my network or system? Can you suggest some commands?

This vulnerability can be detected by monitoring for unusual outbound HTTP requests from the Dalfox REST API server that contain payloads derived from local file contents. Since the exploit involves reading arbitrary files line-by-line and sending them as XSS payloads to an attacker-controlled target, network traffic analysis focusing on unexpected data exfiltration patterns is useful.

To detect exploitation attempts, you can look for HTTP requests to the Dalfox REST API server that include the `custom-payload-file` field in the JSON body with suspicious file paths such as `/etc/passwd` or other sensitive files.

Suggested commands to detect potential exploitation attempts include:

  • Using network traffic capture tools like tcpdump or Wireshark to filter HTTP POST requests to the Dalfox REST API server and inspect JSON payloads for the `custom-payload-file` field.
  • Example tcpdump command to capture HTTP POST requests on port 8080 (replace with actual port): `tcpdump -A -s 0 'tcp dst port 8080 and (((ip[2:2] - ((ip[0]&0xf)<<2)) - ((tcp[12]&0xf0)>>2)) != 0)'`
  • Using grep or jq on server logs to search for JSON requests containing `custom-payload-file` with suspicious file paths: `grep -i 'custom-payload-file' /path/to/dalfox/logs | grep -E '/etc/passwd|id_rsa|env'`
  • Monitoring Dalfox server logs for unauthenticated API requests that include the `custom-payload-file` parameter.

Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart