dbcve.org
CWE-73Weakness · CWE-73

CVE-2026-45089

HIGH · 8.2 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 →
91/100
Remediation priority · Urgent
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 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.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.

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 versions before 2.13.0 running in REST API server mode, the output, output-all, and debug fields in model.Options are deserialized directly from JSON request bodies without validation. These attacker-controlled values are passed to the DalLog function, which opens the specified path using os.O_APPEND|os.O_CREATE|os.O_WRONLY and writes scan logs to it. This file write executes outside the IsLibrary guard, allowing unauthenticated attackers to create or append to any file writable by the dalfox process.

MitigationUpgrade to Dalfox version 2.13.0 or later. If immediate upgrade is not possible, disable the REST API server mode and ensure no unauthenticated network access to any running instance.

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
None
Integrity
High
Availability
Low

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

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 identify the installed version
    Affected if Version is prior to 2.13.0 (e.g., 2.12.0, 2.11.0, etc.)
  2. Confirm REST API server mode is enabled
    Check if Dalfox is running with the 'server' subcommand or similar API mode flag (e.g., 'dalfox server')
    Affected if The REST API server mode is active and accessible to attackers (no API key or authentication)
  3. Verify API endpoint accepts vulnerable parameters
    Send a POST request to the Dalfox API with JSON body containing 'output', 'output-all', or 'debug' fields pointing to an arbitrary file path
    Affected if The API accepts and processes these fields without rejecting them as invalid
  4. Check Dalfox process file permissions
    Review what files the dalfox process user can write to on the system
    Affected if The dalfox process has write permissions to sensitive files that an attacker could target via the file write primitive

You are affected if running Dalfox version prior to 2.13.0 with REST API server mode enabled and accessible without authentication.

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 version 2.13.0 or later. If immediate upgrade is not possible, disable the REST API server mode and ensure no unauthenticated network access to any running instance.

Recommended fix High confidence

2.13.0

  1. Check the currently installed version of dalfox using 'dalfox version' or similar command
  2. Download dalfox version 2.13.0 or later from the official GitHub repository (github.com/hahwul/dalfox)
  3. Install the updated version following the standard installation method for your platform (e.g., go install, binary download, or package manager)
  4. Verify the new version is installed by running 'dalfox version'
  5. If running as a server, restart the dalfox REST API service to ensure the patched binary is active

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,120
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-45089 — 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-45089 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