dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-11851

MEDIUM · 5.9 CVSS v4.0 Published 2026-07-15
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
65/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
Improper Neutralization of Special Elements used in an SQL Command ("SQL Injection") in the web management interface of certain ASUS router models allows a remote authenticated user to disclose confidential information via a crafted request that bypasses existing input validation Refer to the '  Security Update for ASUS Router Firmware ' section on the ASUS Security Advisory for more information.

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 · moderate confidence

SQL injection vulnerability in ASUS router web management interface allows remote authenticated users to bypass input validation through crafted requests, enabling disclosure of confidential information from the database.

MitigationApply the latest ASUS router firmware security update; if unavailable, restrict web management interface access to trusted IP addresses or VPN connections to reduce attack surface.

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
High
Privileges
High
Authentication
X
User interaction
None
Scope
X

CVSS:4.0/AV:N/AC:H/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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. Verify web management interface is enabled
    Log into the ASUS router admin panel and navigate to Administration > System Settings. Look for 'Enable Web GUI' or similar option. Alternatively, check via CLI if accessible: grep -i 'enable_web' /etc/config/* or check nvram variables.
    Affected if The web management interface is enabled and accessible
  2. Confirm remote management access is permitted
    In the router admin panel, check Administration > Remote Access (or similar). Look for options like 'Enable Remote Management', 'Allow WAN Access', or 'HTTPS Remote Access'. Verify if the router accepts management connections from WAN IP addresses.
    Affected if Remote management or WAN access to the web interface is enabled, allowing authenticated users to access the interface from outside the local network
  3. Check for exposure to untrusted networks
    Determine if the router's web interface is reachable from the internet by attempting to access the router's public IP on ports 80/443, or by checking port forwarding/NAT rules. Also check if VPN or DDNS features are configured that allow external access.
    Affected if The web management interface is exposed to the internet or untrusted networks rather than only accessible via LAN or VPN
  4. Assess authentication mechanisms
    Review the router's user accounts and authentication settings in the admin panel under Administration > Account or similar. Determine if default credentials are in use or if multiple user accounts exist with varying privilege levels.
    Affected if Weak or default authentication credentials are configured, making unauthorized authenticated access more likely
  5. Review input handling in custom configurations
    Examine any custom firewall rules, scripts, or iptables configurations that may interact with the web interface: check /jffs/scripts/, /tmp, or similar locations for user-defined handlers that process web form inputs.
    Affected if Custom scripts or configurations handle web interface inputs without proper sanitization

A user is affected if the ASUS router has its web management interface enabled and accessible to remote authenticated users, particularly if WAN/remote access is permitted or the interface is internet-facing.

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 latest ASUS router firmware security update; if unavailable, restrict web management interface access to trusted IP addresses or VPN connections to reduce attack surface.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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