CVE-2025-13798
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 · uneditedA flaw has been found in ADSLR NBR1005GPEV2 250814-r037c. This affects the function ap_macfilter_add of the file /send_order.cgi. Executing manipulation of the argument mac can lead to command injection. The attack may be performed from remote. The exploit has been published 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 confidenceA command injection vulnerability exists in the ap_macfilter_add function of /send_order.cgi on ADSLR NBR1005GPEV2 devices (firmware 250814-r037c). The 'mac' parameter is not properly sanitized before being used in OS command execution, allowing remote unauthenticated attackers to inject arbitrary shell commands.
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<= 250814-r037cCVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelLocate the device label or check the web interface footer/admin page for the model number. Confirm it is an ADSLR NBR1005GPEV2 or Adslr B Qe2w401 device.Affected if The device model matches NBR1005GPEV2 or Qe2w401
-
Determine the firmware versionAccess the device web administration interface and navigate to the system status or firmware upgrade page to view the installed firmware version. Alternatively, check the firmware file name if you have access to it.Affected if The firmware version is 250814-r037c or earlier
-
Verify the web interface is accessibleAttempt to access http://[device-ip]/send_order.cgi from an authorized management network. Confirm the CGI endpoint responds.Affected if The /send_order.cgi endpoint is reachable and responds to requests
-
Check if MAC filtering feature is enabledLog into the device web interface and navigate to the wireless or MAC filtering settings section. Look for the MAC filter configuration.Affected if MAC filtering is enabled or configurable on the device
The device is affected if it is an ADSLR NBR1005GPEV2 or Qe2w401 model running firmware version 250814-r037c or earlier, and the web interface with /send_order.cgi is accessible.
Generated from the published advisory. Verify against your own configuration.
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 dataImmediately restrict network access to the device's web interface (e.g., firewall/ACLs). Since the vendor did not respond, consider isolating the device or replacing it with a supported alternative. If external access is required, implement strict ACLs at the network perimeter.
- Consultation4.0 h
- Implementation8.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-13798 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-13798 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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