dbcve.org
CWE-73Weakness · CWE-73

CVE-2026-45088

HIGH · 7.5 CVSS v3.1 Published 2026-05-27
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Dalfox before 2.13.0, the REST API server mode deserializes the custom-payload-file parameter directly from unauthenticated JSON request bodies without validation. Attackers can specify arbitrary file paths which get read by voltFile.ReadLinesOrLiteral, and file contents are embedded as XSS payloads in outbound HTTP requests, enabling file exfiltration.

MitigationUpgrade to Dalfox 2.13.0 or later. Until patched, do not expose the REST API server to untrusted networks and consider whether API key authentication can be enabled as a compensating control.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Dalfox version
    Run 'dalfox version' or 'dalfox --version' to determine the installed version
    Affected if Version is before 2.13.0 (e.g., 2.12.0, 2.11.0, earlier)
  2. Identify if REST API server mode is enabled
    Check if Dalfox is running with 'server' subcommand or API flags (e.g., dalfox server)
    Affected if The REST API server mode is actively running or configured to run
  3. Verify API key authentication configuration
    Check if an API key has been configured via --api-key flag or configuration file for the server mode
    Affected if No API key is configured and the REST API is accessible to attackers
  4. Assess network exposure of REST API
    Determine whether the REST API listener is bound to 0.0.0.0 or a publicly accessible IP address versus localhost/127.0.0.1
    Affected if The REST API is exposed to untrusted or public networks without authentication

You are affected if running Dalfox version below 2.13.0 with the REST API server mode enabled and accessible to untrusted attackers without API key protection.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Dalfox 2.13.0 or later. Until patched, do not expose the REST API server to untrusted networks and consider whether API key authentication can be enabled as a compensating control.

Recommended fix High confidence

2.13.0

  1. 1. Check the current installed version of dalfox using 'dalfox version'
  2. 2. If the version is below 2.13.0 and the REST API server mode is in use, upgrade to version 2.13.0 or later
  3. 3. Download the updated dalfox binary from the official GitHub repository (github.com/hahwul/dalfox)
  4. 4. Replace the existing dalfox binary with the new version
  5. 5. Restart any running dalfox REST API server instances

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45088 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-45088 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data