dbcve.org
B Qe2w401 FirmwareOperating system · Adslr

CVE-2025-13797

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-01
Fix available
A fix is available. Upgrade to after 250814-r037c or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit 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
A vulnerability was detected in ADSLR B-QE2W401 250814-r037c. Affected by this issue is the function parameterdel_swifimac of the file /send_order.cgi. Performing manipulation of the argument del_swifimac results in command injection. The attack is possible to be carried out remotely. The exploit is now public and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

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

Command injection vulnerability in the del_swifimac parameter of /send_order.cgi on ADSLR B-QE2W401 firmware 250814-r037c allows remote attackers to inject and execute arbitrary operating system commands due to insufficient input validation.

MitigationIsolate the affected device behind a firewall or network segmentation; restrict access to the management interface to trusted IPs only; implement ingress filtering at upstream network devices to block malicious requests to /send_order.cgi until vendor firmware patch is available.

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
B Qe2w401 FirmwareOperating system
Affected:<= 250814-r037c

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
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/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 device model
    Locate the device label or check the web management interface for the model number B-QE2W401 or similar Adslr branding
    Affected if The device is an Adslr B-QE2W401 unit
  2. Check installed firmware version
    Access the device web interface or check system settings for the firmware build number. Compare against the affected version 250814-r037c or earlier
    Affected if Firmware version is 250814-r037c or any version lower (earlier) than it
  3. Verify web management interface is accessible
    Attempt to access the device HTTP/HTTPS management interface from a remote host or check if the web service is listening on the device
    Affected if The web management interface responds to requests
  4. Confirm presence of vulnerable endpoint
    Check if the URI /send_order.cgi is accessible on the device web server
    Affected if The /send_order.cgi endpoint responds to requests
  5. Assess network exposure of management interface
    Determine if the device management interface is reachable from untrusted networks or directly from the internet
    Affected if The management interface is accessible from untrusted networks or the internet

The device is affected if it is an Adslr B-QE2W401 with firmware version 250814-r037c or earlier and the /send_order.cgi endpoint is accessible on the network.

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
Upgrade available Upgrade to a release after 250814-r037c
Interim mitigation

Isolate the affected device behind a firewall or network segmentation; restrict access to the management interface to trusted IPs only; implement ingress filtering at upstream network devices to block malicious requests to /send_order.cgi until vendor firmware patch is available.

Recommended fix High confidence
  1. Isolate the affected device (B-QE2W401) on a restricted network segment to limit exposure to untrusted users
  2. Place the device behind a firewall and restrict access to the management interface (HTTP/HTTPS ports) to only trusted IP addresses
  3. If remote access is required, implement VPN authentication before permitting any access to the device's web interface
  4. Monitor network traffic for suspicious requests to /send_order.cgi, particularly those containing the del_swifimac parameter
  5. Consider replacing the affected device with an alternative product from a vendor that provides security updates
  6. Document the risk and accept it in writing if the device must remain in production without vendor patches
Caveat No vendor patch or firmware fix is available; the vendor (ADSLR) did not respond to the disclosure

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

Fix this in B Qe2w401 Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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