dbcve.org
CWE-15Weakness · CWE-15

CVE-2026-45087

CRITICAL · 10.0 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 →
100/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 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. 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, the REST API server mode (dalfox server) binds to 0.0.0.0:6664 without requiring authentication by default. The model.Options struct including FoundAction and FoundActionShell fields is deserialized directly from attacker-supplied JSON in POST /scan requests and passed through to dalfox.Initialize without sanitization. This allows any unauthenticated attacker who can reach the server port to inject arbitrary shell commands that execute on the host whenever a scan finding is triggered.

MitigationUpgrade to Dalfox 2.13.0 or later. If unable to upgrade immediately, ensure the server is not exposed to untrusted networks and implement API key authentication via --api-key flag 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
Changed
Confidentiality
High
Integrity
High
Availability
High

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

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. Identify if dalfox server mode is running
    Check for running processes or containers executing 'dalfox server' command, or look for processes listening on port 6664 using commands like 'netstat -tlnp' or 'ss -tlnp'
    Affected if The dalfox server process is active and listening on a network port
  2. Determine installed dalfox version
    Run 'dalfox version' or 'dalfox --version' and compare the output to 2.13.0
    Affected if The version number is lower than 2.13.0 (for example, 2.12.0, 2.11.0, etc.)
  3. Verify if API key authentication is configured
    Review the command line arguments or environment variables used when starting dalfox server; check for the presence of --api-key flag with a value
    Affected if The --api-key flag is not set or not used when starting the server, meaning authentication is disabled
  4. Check network binding configuration
    Examine the listening address: if dalfox server binds to 0.0.0.0 or an external interface IP rather than 127.0.0.1, the service is network-accessible
    Affected if The server binds to 0.0.0.0 or a non-loopback address, making it reachable from other hosts

A user is affected if they are running dalfox server with a version before 2.13.0 that is network-accessible without API key authentication configured.

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. If unable to upgrade immediately, ensure the server is not exposed to untrusted networks and implement API key authentication via --api-key flag as a compensating control.

Recommended fix High confidence

2.13.0

  1. 1. Stop any running dalfox server instances
  2. 2. Upgrade dalfox to version 2.13.0 or later using your package manager or by downloading the release from the official GitHub repository
  3. 3. Verify the installed version with: dalfox version
  4. 4. If using the REST API server mode, consider adding an API key using the --api-key flag for additional security
  5. 5. Restart the dalfox server with the updated version

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,770
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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