dbcve.org
Wf 500 FirmwareOperating system · Waterfall Security

CVE-2025-41265

HIGH · 7.2 CVSS v3.1 Published 2026-05-29
Fix available
A fix is available. Upgrade to after 7.9.1.0_r2502171040 or later.
See remediation →
78/100
Remediation priority · High
Remotely reachable 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
Nozomi Networks Labs identified a CWE-78: Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection') in the Administration WebUI in Waterfall WF-500 TX Host in version 7.9.1.0 R2502171040 that allows remote authenticated attackers to execute arbitrary operating system commands on the WF-500 TX Host.

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

An OS Command Injection vulnerability (CWE-78) exists in the Administration WebUI of Waterfall WF-500 TX Host version 7.9.1.0 R2502171040. Remote authenticated attackers can execute arbitrary operating system commands due to improper neutralization of special elements in user input processed by the WebUI interface.

MitigationApply vendor-provided patch or firmware update for version 7.9.1.0 R2502171040. Until patch is available, restrict administrative WebUI access to minimal necessary personnel and monitor for suspicious command execution patterns.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wf 500 FirmwareOperating system
Affected:<= 7.9.1.0_r2502171040

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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 the Waterfall WF-500 TX Host device
    Locate the physical device or network asset and confirm it is a Waterfall Security WF-500 TX Host. Check device label, management console, or network inventory for the exact model number.
    Affected if The device is not a Waterfall WF-500 TX Host, then this specific CVE does not apply.
  2. Determine the installed firmware version
    Access the device console or web interface and navigate to System Information or Firmware Details. Look for a version string such as '7.9.1.0_r2502171040' or similar. Compare your version to the affected range: any version <= 7.9.1.0_r2502171040 is vulnerable.
    Affected if The firmware version is 7.9.1.0_r2502171040 or earlier (lower version numbers).
  3. Verify the Administration WebUI is enabled
    Log into the device management interface and check the WebUI service status. Confirm that the Administration WebUI feature is currently active and accessible.
    Affected if The Administration WebUI is enabled and reachable on the network.
  4. Check network exposure of the Administration WebUI
    Review firewall rules, access control lists, or network segmentation settings to determine if the Administration WebUI port (typically HTTP/HTTPS) is exposed to untrusted networks or the internet.
    Affected if The Administration WebUI is accessible from untrusted networks or directly from the internet.
  5. Confirm administrative authentication is configured
    Check if local or remote administrative accounts are configured and enabled for the WebUI. Verify that authentication mechanisms are active.
    Affected if Administrative accounts exist and authentication is enabled, as the vulnerability requires authenticated access.

You are affected if you have a Waterfall WF-500 TX Host running firmware version 7.9.1.0_r2502171040 or earlier, with the Administration WebUI enabled and accessible (even with valid admin credentials).

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.

From vendor data
Upgrade available Upgrade to a release after 7.9.1.0_r2502171040
Interim mitigation

Apply vendor-provided patch or firmware update for version 7.9.1.0 R2502171040. Until patch is available, restrict administrative WebUI access to minimal necessary personnel and monitor for suspicious command execution patterns.

Fix this in Wf 500 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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