dbcve.org
InjectionWeakness · CWE-74

CVE-2025-11045

HIGH · 7.3 CVSS v3.1 Published 2025-09-26
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
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 identified in WAYOS LQ_04, LQ_05, LQ_06, LQ_07 and LQ_09 22.03.17. This affects an unknown function of the file /usb_paswd.asp. The manipulation of the argument Name leads to command injection. The attack can be initiated remotely. The exploit is publicly available and might be used.

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 WAYOS router firmware (LQ_04-LQ_09, build 22.03.17). The /usb_paswd.asp file fails to sanitize the 'Name' parameter before passing it to system command execution, allowing remote attackers to inject and execute arbitrary OS commands.

MitigationApply vendor firmware patch if available; otherwise restrict network access to the management interface or disable the vulnerable /usb_paswd.asp endpoint at the network edge.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 the device as a WAYOS router
    Access the router web interface or check the device model/firmware banner for 'WAYOS' branding
    Affected if The device is a WAYOS router running the affected firmware line
  2. Check the firmware version
    Navigate to the router admin panel status page or use telnet/SSH to run 'version' or 'cat /proc/version' to retrieve the firmware build information
    Affected if The firmware version falls within LQ_04 through LQ_09 on build 22.03.17
  3. Verify the vulnerable endpoint exists
    Attempt to access http://<router_ip>/usb_paswd.asp via HTTP request
    Affected if The endpoint returns a valid page rather than a 404 error, indicating the vulnerable script is present
  4. Test for command injection in the Name parameter
    Send a crafted request to /usb_paswd.asp with a benign payload in the Name parameter (such as adding a non-destructive test string like ';echo test;')
    Affected if The response reflects executed command output or shows evidence of command execution beyond the expected parameter handling

A user is affected if they operate a WAYOS router on firmware builds LQ_04-LQ_09 (build 22.03.17) where the /usb_paswd.asp endpoint is accessible and the Name parameter executes injected OS commands.

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 vendor firmware patch if available; otherwise restrict network access to the management interface or disable the vulnerable /usb_paswd.asp endpoint at the network edge.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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