Command InjectionWeakness · CWE-77

CVE-2026-13560

MEDIUM · 6.3 CVSS v3.1 Published 2026-06-29
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 7 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 vulnerability has been detected in Edimax EW-7478APC 1.04. The affected element is the function formAccept of the file /goform/formAccept of the component POST Request Handler. The manipulation of the argument submit-url leads to os command injection. The attack is possible to be carried out remotely. The exploit has been disclosed publicly 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

OS command injection vulnerability in Edimax EW-7478APC 1.04 router firmware. The formAccept function in /goform/formAccept POST handler fails to properly sanitize the submit-url parameter, allowing attackers to inject arbitrary OS commands remotely.

MitigationSince Edimax did not respond to disclosure, no vendor patch exists. Mitigation requires network access restrictions (firewall/ACLs) to limit exposure, or replacement with a supported device. If继续使用,需进行固件逆向工程以实施输入验证修补。

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
    Access the router web interface or check the device label/sticker for the model number EW-7478APC. Alternatively, check DHCP logs or network scan results for this specific model identifier.
    Affected if Device is not an Edimax EW-7478APC router - the vulnerability does not apply to other models.
  2. Check firmware version
    Log into the router web interface and navigate to System Status or Firmware Upgrade page to view the firmware version. The affected version is 1.04.
    Affected if Firmware version is 1.04 - this is the only version listed as affected in the provided data.
  3. Verify web interface is enabled
    Attempt to access the router's HTTP administration interface on the default IP (typically 192.168.2.1). The vulnerability requires the web-based management interface to be active.
    Affected if The web management interface returns a login page or responds to HTTP requests - the command injection targets this web handler.
  4. Confirm vulnerable endpoint exists
    Send a POST request to /goform/formAccept with a test parameter. The vulnerability is in the formAccept POST handler processing the submit-url parameter.
    Affected if The /goform/formAccept endpoint responds to POST requests - this is the vulnerable handler.
  5. Assess network exposure
    Determine if the router management interface is accessible from untrusted networks (WAN/internet). Check port forwarding rules, firewall configurations, or if the device is directly exposed to the internet.
    Affected if The router's web interface is accessible from the WAN/internet - the vulnerability is remotely exploitable.

A user is affected if they are running Edimax EW-7478APC firmware version 1.04 with the web management interface enabled and accessible, particularly if 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

Since Edimax did not respond to disclosure, no vendor patch exists. Mitigation requires network access restrictions (firewall/ACLs) to limit exposure, or replacement with a supported device. If继续使用,需进行固件逆向工程以实施输入验证修补。

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-13560 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