← Back to Feed CACHED · 2026-10-02 00:06:07 · CACHE_KEY CVE-2026-13563
CVE-2026-13563 · CWE-119 · Disclosed 2026-06-29

Edimax EW-7478APC Stack-Based Buffer Overflow in formL2TPSetup (L2TPUserName)

ASSESSED — NOISGATE
Vendor
—
—
—
Reassessed
—
—
—
Verdict: —
Do you agree?
01 · The Real Story

Like worrying about a broken lock on a shed that was demolished six years ago

CVE-2026-13563 is a stack-based buffer overflow in the formL2TPSetup function of the Edimax EW-7478APC AC1200 wireless access point, firmware version 1.04. An authenticated attacker sends a crafted POST request to /goform/formL2TPSetup with an oversized L2TPUserName parameter, overwriting the return address on the stack and achieving remote code execution on the embedded device. The device's default credentials are admin / 1234, making the PR:L requirement essentially free on unmodified installs. This is one of at least ten CVEs disclosed against this same firmware version in mid-2026 (CVE-2026-13561 through 13564, 13581, 13583, 19959–19963), covering buffer overflows *and* command injection across virtually every /goform/ handler. The device is riddled with vulnerabilities.

The vendor's 8.8 HIGH score is technically correct for the *device itself* — it's an authenticated network RCE with low complexity. But vendor severity ignores deployment context. The EW-7478APC is a consumer/SOHO access point from a minor Taiwanese brand, discontinued on January 10, 2020, with no firmware updates, no technical support, and no enterprise presence to speak of. Its management interface listens on 192.168.2.1 and is LAN-only by default. For an enterprise security team managing 10,000 hosts, the probability of this device existing in your fleet is near zero. If it does exist, it's been running unsupported firmware for six-plus years and should have been decommissioned long ago — the CVE is just one more reason. The vendor HIGH rating wildly overstates the risk to any real enterprise.

"EoL consumer AP from a niche vendor — if you have one, rip it out; odds are you don't"
02 · The Attack Path

4 steps from start to impact.

STEP 01

Gain LAN access to the AP's management subnet

The attacker must be on the same Layer 2/Layer 3 segment as the EW-7478APC's management interface (default 192.168.2.1). This requires either physical proximity to the wireless network, a compromised host on the same VLAN, or the rare case of remote management being explicitly enabled. Enterprise networks that segment IoT/consumer gear onto isolated VLANs make this step harder.
Conditions required:
  • Network adjacency or prior compromise of a host on the same subnet
  • Management interface reachable (default: LAN-only, port 80)
Where this breaks in practice:
  • Enterprise networks typically segment or prohibit consumer APs entirely
  • The device is a consumer AP — unlikely to be on a managed corporate network
  • Remote management is disabled by default
Detection/coverage: Network asset inventory should flag unknown consumer APs via 802.1X NAC or rogue AP detection (Cisco ISE, Aruba ClearPass, etc.)
STEP 02

Authenticate to the web management interface

The CVSS vector requires PR:L — a valid login to the web UI. However, the EW-7478APC ships with default credentials admin / 1234, which are widely documented. If the owner never changed them (common for consumer gear), this step is trivial. An attacker can also attempt brute-force since the web UI has no rate limiting or lockout mechanism.
Conditions required:
  • Valid credentials for the web UI (or unchanged defaults)
Where this breaks in practice:
  • If credentials were changed to something strong, brute-force is slow over HTTP on embedded hardware
  • No known credential bypass — authentication IS required
Detection/coverage: HTTP login attempts to 192.168.2.1 on port 80; unlikely to be monitored in consumer deployments
STEP 03

Send crafted POST to /goform/formL2TPSetup

The attacker sends an HTTP POST request to /goform/formL2TPSetup with an oversized L2TPUserName parameter. The formL2TPSetup handler performs no bounds checking on this input before copying it to a fixed-size stack buffer, causing a classic stack-based buffer overflow (CWE-121). The attacker overwrites the saved return address with a controlled value. The public disclosure material (hosted on Notion) contains sufficient detail to reproduce the crash.
Conditions required:
  • Authenticated session from Step 2
  • Knowledge of the vulnerable endpoint and parameter (publicly documented)
Where this breaks in practice:
  • Payload must be crafted for the specific MIPS/ARM architecture of this embedded device
  • Firmware version 1.04 is the only confirmed affected version
Detection/coverage: WAF or IDS rules for oversized POST parameters to /goform/ endpoints — but consumer APs are not behind WAFs
STEP 04

Achieve code execution on the AP

Successful exploitation gives the attacker arbitrary code execution as root on the embedded Linux OS running the access point. From here, the attacker can intercept all wireless traffic passing through the AP, inject responses, pivot to other devices on the network, or brick the device. The blast radius is limited to the single AP and the wireless clients connected to it.
Conditions required:
  • Successful stack smash from Step 3
  • Payload compatible with the device's CPU architecture and firmware layout
Where this breaks in practice:
  • Embedded device exploitation requires architecture-specific shellcode
  • No ASLR or stack canaries on this class of consumer firmware, which actually makes exploitation easier
  • Impact is limited to a single consumer AP and its connected clients
Detection/coverage: Anomalous traffic from the AP's management IP; firmware integrity checks (not available on this device)
03 · Compensating Control

1
LOW 3.5→IGNORE 0.0
SEVERITY REDUCED
Decommission the device immediately — The EW-7478APC has been end-of-life since January 2020 and will never receive a firmware update. It has 10+ unpatched CVEs covering RCE and command injection. The only effective remediation is physical removal and replacement with a supported enterprise AP (e.g., Cisco Catalyst, Aruba Instant On, Meraki). As a LOW-severity item under the noisgate SLA, this is backlog hygiene with no mitigation deadline — but given the device is EoL with no possible patch, treat decommission as your remediation action.
2
LOW 3.5→LOW 2.0
Isolate the device on a quarantine VLAN — If immediate removal is not possible, place the AP on an isolated VLAN with no route to corporate resources. Block all inbound traffic to 192.168.2.1:80 from anything except a dedicated management jump host. This breaks Step 1 of the attack path by preventing LAN-adjacent exploitation from compromised corporate hosts.
3
LOW 3.5→LOW 3.0
Change default credentials — Replace the default admin/1234 credentials with a strong, unique password. This raises the bar for Step 2 from trivial to requiring brute-force, which is slow on embedded hardware. Does not fix the underlying vulnerability but removes the easiest exploitation path.
4
LOW 3.5→LOW 3.0
Disable L2TP configuration via web UI — If the device allows disabling the L2TP setup page or restricting access to /goform/formL2TPSetup, do so. This removes the specific attack surface for CVE-2026-13563. However, note that 10+ sibling CVEs exist on other /goform/ handlers, so this only addresses one of many entry points.
What doesn't work
  • Firmware update — no patch exists and none will be released. The vendor is unresponsive and ended support in 2020.
  • WAF / IPS in front of the device — the management interface is a local HTTP service on an embedded AP. Deploying a WAF in front of it is architecturally nonsensical for a consumer AP.
  • EDR on the device — this is an embedded Linux appliance with no agent support. Endpoint detection tools cannot be installed.
  • Vulnerability scanning alone — scanners may flag the firmware version, but there is no remediation path other than replacement. Scanning without a decommission plan is theater.
04 · Intelligence Metadata

The supporting signals.

In-the-Wild ExploitationNo evidence. Not listed in CISA KEV. No reports of active exploitation in campaigns. The device's tiny installed base makes it an unattractive target for broad exploitation.
Proof of ConceptPublic. Disclosure material hosted on Notion (lavender-bicycle-a5a.notion.site) contains technical details sufficient to reproduce the overflow. No dedicated GitHub PoC repo found for this specific CVE. The exploit has been described as "disclosed to the public and may be used" per VulDB. Not indexed on pocindex.io as a standalone exploit.
EPSS Score0.00805 (0.805%) — 54th percentile. Below the threshold that typically triggers urgency. Reflects the low likelihood of exploitation in the wild given the niche target.
KEV StatusNot listed. No CISA Known Exploited Vulnerabilities catalog entry.
CVSS VectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H — 8.8 HIGH. Network-accessible, low complexity, requires low-privilege auth, no user interaction. Full CIA impact. The vector is accurate *for the device*; it does not capture the near-zero enterprise installed base.
Affected VersionsEdimax EW-7478APC firmware 1.04 (only confirmed version). This is the final firmware release — the device was discontinued January 10, 2020.
Fixed VersionNone. Will never exist. Edimax ended all support for this product on January 10, 2020. The vendor was contacted about this CVE and "did not respond in any way."
Scanning / ExposureNo Shodan/Censys/GreyNoise data specific to this model found. The management interface is LAN-only by default (HTTP on 192.168.2.1:80). Internet-facing exposure is expected to be negligible.
Related CVEsThis device has 10+ CVEs disclosed in the same June 2026 wave: CVE-2026-13561–13564, 13581, 13583, 19959–19963. They cover buffer overflows *and* OS command injection across nearly every /goform/ handler. The entire firmware is compromised by design.
Disclosure / ResearcherDisclosed 2026-06-29 via VulDB submission and Notion writeup. Researcher identity not publicly attributed. Vendor notification attempted with no response.

Sources.

  1. OpenCVE — CVE-2026-13563 Details
  2. CyberStrike — CVE-2026-13563 Detail Page
  3. Hol Security — CVE-2026-13563 Edimax EW-7478APC formL2TPSetup
  4. Edimax EOS Announcement — Discontinued Products
  5. Edimax EW-7478APC Product Page
  6. Modemly — Edimax EW-7478APC Default Credentials
  7. SpeedGuide — Edimax EW-7478APC Specifications
05 · The Call

Final Verdict
↓ DOWNGRADED to LOW (3.5/10)

Why this verdict

  • Near-zero enterprise installed base: The Edimax EW-7478APC is a consumer/SOHO AC1200 wireless access point from a minor Taiwanese brand. It is not sold through enterprise channels, not supported by any enterprise WLAN management platform, and has been discontinued since January 2020. The probability of this device existing in a managed 10,000-host environment is effectively zero.
  • LAN-only management interface: The web UI is accessible only at 192.168.2.1 on the local subnet by default. Exploitation requires the attacker to already be on the same network segment — meaning post-initial-access or physical proximity. This compounding prerequisite significantly narrows the reachable population.
  • Authentication required (but weakened by defaults): PR:L is the CVSS prerequisite, and default credentials (admin/1234) make it trivial on unmodified devices. This friction point is nearly absent in practice, so no upward adjustment is warranted — but it doesn't lower the score either.
  • Role multiplier: The EW-7478APC is a consumer wireless access point. It does not occupy any high-value enterprise role: it is not a network edge appliance (no firewall/VPN), not an identity provider, not a hypervisor, not a CI/CD system, not a backup target, and not a production database. The blast radius of compromise is limited to a single AP and its connected wireless clients. No high-value-role floor applies. Even as a network device, its compromise does not grant domain-level, fleet-level, or supply-chain-level impact.
  • No patch, but irrelevant: The lack of a vendor fix normally increases urgency, but when the device has been EoL for 6+ years and has near-zero enterprise presence, the correct action is decommission — not patch-tracking.

Why not higher?

The device is a full-RCE target with public exploit material and default credentials, which would normally warrant at least MEDIUM. However, the near-zero enterprise installed base, LAN-only attack surface, consumer-grade product category, and absence of any high-value deployment role all compound to make this a LOW-priority item for any enterprise security team. There is no plausible scenario where this consumer AP occupies a role whose compromise leads to domain takeover, fleet compromise, or supply-chain impact.

Why not lower?

Despite the negligible enterprise relevance, the vulnerability is a genuine unauthenticated-equivalent RCE (default creds) with public exploit material on a device that will never receive a patch. If a defender discovers one of these APs on their network, it represents an unmitigable risk that must be addressed by removal. The device also has 10+ sibling CVEs confirming the firmware is fundamentally insecure. This prevents an IGNORE rating — if found, it demands action.

06 · Verification

Crowdsourced verification payload.

Run this script from any Linux/macOS host on the same subnet as the Edimax AP. It checks whether the device is reachable and running the vulnerable firmware version by probing the web UI. No authentication is required for the version check. Usage: bash check_cve_2026_13563.sh 192.168.2.1

noisgate-verify.sh
BASHREAD-ONLYSAFE
#!/usr/bin/env bash
# check_cve_2026_13563.sh — Detect Edimax EW-7478APC vulnerable to CVE-2026-13563
# Usage: bash check_cve_2026_13563.sh <TARGET_IP>
# Requires: curl
# Exit codes: 0=VULNERABLE, 1=PATCHED/NOT_AFFECTED, 2=UNKNOWN

set -euo pipefail

TARGET="${1:-}"
if [[ -z "$TARGET" ]]; then
  echo "Usage: $0 <TARGET_IP>"
  exit 2
fi

echo "[*] Probing $TARGET for Edimax EW-7478APC ..."

# Attempt to fetch the login/status page
RESPONSE=$(curl -sk --connect-timeout 5 --max-time 10 "http://${TARGET}/" 2>/dev/null || true)

if [[ -z "$RESPONSE" ]]; then
  echo "[?] UNKNOWN — could not reach http://${TARGET}/"
  exit 2
fi

# Check if this is an Edimax device
if ! echo "$RESPONSE" | grep -qi 'edimax'; then
  echo "[−] PATCHED / NOT AFFECTED — device at $TARGET is not an Edimax AP"
  exit 1
fi

# Check for EW-7478APC model identifier
if ! echo "$RESPONSE" | grep -qi 'EW-7478APC'; then
  echo "[−] PATCHED / NOT AFFECTED — Edimax device at $TARGET is not model EW-7478APC"
  exit 1
fi

# Check for firmware version 1.04
if echo "$RESPONSE" | grep -qi '1\.04'; then
  echo "[!] VULNERABLE — Edimax EW-7478APC firmware 1.04 detected at $TARGET"
  echo "    CVE-2026-13563: Stack-based buffer overflow in formL2TPSetup (L2TPUserName)"
  echo "    Action: Decommission this device immediately. No patch exists (EoL since 2020-01-10)."
  exit 0
fi

# Check for the vulnerable endpoint
ENDPOINT=$(curl -sk --connect-timeout 5 --max-time 10 -o /dev/null -w '%{http_code}' "http://${TARGET}/goform/formL2TPSetup" 2>/dev/null || echo "000")

if [[ "$ENDPOINT" == "200" || "$ENDPOINT" == "401" || "$ENDPOINT" == "403" ]]; then
  echo "[!] VULNERABLE — Edimax EW-7478APC detected at $TARGET with formL2TPSetup endpoint present"
  echo "    CVE-2026-13563: Stack-based buffer overflow in formL2TPSetup (L2TPUserName)"
  echo "    Action: Decommission this device immediately. No patch exists (EoL since 2020-01-10)."
  exit 0
fi

echo "[?] UNKNOWN — Edimax EW-7478APC detected but could not confirm firmware version"
exit 2