dbcve.org
Command InjectionWeakness · CWE-77

CVE-2026-15513

MEDIUM · 6.3 CVSS v3.1 Published 2026-07-13
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
69/100
Remediation priority · Elevated
Remotely reachable Zero-click 5 weeks old

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 security flaw has been discovered in Wavlink WL-NU516U1 260515. This affects the function wlink_uci_set_value of the file /cgi-bin/adm.cgi. Performing a manipulation of the argument lan_ip results in os command injection. The attack can be initiated remotely. The exploit has been released to the public and may be used for attacks. You should upgrade the affected component. The vendor was contacted early, responded in a very professional manner and quickly released a fixed version of the affected product.

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

OS command injection vulnerability in Wavlink WL-NU516U1 router firmware (260515). The wlink_uci_set_value function in /cgi-bin/adm.cgi fails to sanitize the lan_ip parameter, allowing remote attackers to inject and execute arbitrary OS commands. A public exploit exists, increasing exploit likelihood.

MitigationApply the vendor-supplied firmware update to the latest patched version. If immediate patching is not feasible, disable remote administrative access to the device or restrict access to trusted IP addresses until the update can be applied.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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. Identify device model and firmware version
    Access the router administration interface and navigate to System Status or Firmware Version page. Alternatively, check the label on the device or use Nmap service detection to fingerprint the device.
    Affected if The device is a Wavlink WL-NU516U1 router running firmware version 260515.
  2. Verify the vulnerable CGI script exists
    Attempt to access the URI /cgi-bin/adm.cgi on the device. This can be done with a web request: curl http://TARGET_IP/cgi-bin/adm.cgi
    Affected if The device responds with the adm.cgi script, indicating the vulnerable endpoint is present.
  3. Check if remote admin access is enabled
    In the router web interface, go to Administration or Remote Management settings. Look for options like 'Remote Management', 'Allow remote access', or Web UI port configuration.
    Affected if Remote administrative access is enabled, allowing unauthenticated or low-privilege attackers to reach the CGI interface from external networks.
  4. Assess network exposure of the admin interface
    Determine if the router WAN IP is directly accessible from untrusted networks. Use external port scanning tools or check if the device is behind a NAT/firewall that permits inbound HTTP traffic to port 80 or 443.
    Affected if The router admin interface (port 80/443) is exposed to the internet or untrusted LAN segments.
  5. Look for indicators of compromise
    Review router system logs for unusual commands, unexpected processes, or shell command executions. Check for new user accounts, modified startup scripts, or outbound connections to unknown IPs.
    Affected if Logs show execution of arbitrary commands, new administrative accounts, or post-exploitation activity.

The environment is affected if it is a Wavlink WL-NU516U1 router with firmware 260515 that has its /cgi-bin/adm.cgi interface exposed to untrusted networks.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor-supplied firmware update to the latest patched version. If immediate patching is not feasible, disable remote administrative access to the device or restrict access to trusted IP addresses until the update can be applied.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,600
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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