Summary
Mercusys AC12G (EU) V1 routers expose most UPnP IGD actions on port 1900 without any authentication, including the ability to add port mappings and query external IP information.
When UPnP is enabled (which is the default), any device on the local network can silently create arbitrary port forwarding rules and access WAN traffic statistics, significantly weakening the network boundary.
Affected context
This vulnerability affects Mercusys AC12G (EU) V1 routers running firmware AC12G(EU)_V1_200909 when UPnP (Universal Plug and Play) is enabled via the router's administrative interface.
In this configuration, the router listens on the standard UPnP SSDP/IGD port (1900) and exposes 15 of 18 IGD control actions—including AddPortMapping and GetExternalIPAddress—without verifying the identity or permissions of the requesting client.
The issue is relevant anywhere untrusted or semi‑trusted devices share the same LAN segment, such as home networks, small offices, or guest Wi‑Fi environments.
Exploit preconditions
- Attack surface: UPnP IGD service on UDP/TCP port 1900 of the router, reachable from any device on the local network.
- Required access: Network adjacency to the router (ability to send UPnP requests from the LAN or any segment that can reach port 1900).
- Configuration requirements: UPnP enabled through the router's web interface (enabled by default on affected firmware).
- Trigger point: Sending crafted UPnP/IGD control messages invoking actions such as AddPortMapping or GetExternalIPAddress.
- Why exploitation is possible: The router does not enforce authentication or robust access control on critical UPnP IGD actions, allowing any LAN host to issue privileged configuration changes.
Why this happens
The core issue is a lack of authentication and authorization checks on sensitive UPnP Internet Gateway Device (IGD) actions.
The firmware exposes critical operations—such as creating or modifying port mappings and querying WAN interface details—without verifying whether the caller is trusted or authorized.
This maps to CWE-306: Missing Authentication for Critical Function, where operations that directly affect security boundaries (like NAT and firewall behavior) are callable by any network-adjacent device.
Conceptually, the router treats the local network as entirely trusted and relies on location alone (being on the LAN) as a proxy for identity, instead of requiring explicit credentials, capability checks, or a stricter UPnP security model.
Potential impact
- LAN devices may create arbitrary port forwarding rules, exposing internal services to the internet.
- Attackers on the LAN can weaken or bypass the router's NAT/firewall boundary, enabling inbound connections to otherwise hidden hosts.
- Malware on a compromised LAN device can persistently open backdoors for remote control from the WAN.
- Internal services (e.g., webcams, NAS, admin interfaces) can be unintentionally or maliciously published to the public internet.
- Unauthorized access to WAN connection details and traffic statistics could aid reconnaissance or targeted attacks.
- Increased risk of participation in botnets or DDoS campaigns via exposed services.
General mitigation guidance
Mitigation focuses on hardening the router's control surface and reducing implicit trust in LAN-originated configuration traffic.
Pattern-based defensive approaches include:
- Disable or restrict UPnP in untrusted environments: Where feasible, turn off UPnP entirely or limit it to specific trusted VLANs or interfaces, reducing the attack surface.
- Enforce authentication for critical actions: Design UPnP control endpoints so that operations affecting NAT, firewall, and routing configuration require authentication or cryptographic authorization, instead of relying solely on network location.
- Apply principle of least privilege to UPnP capabilities: Provide only the minimal IGD actions required for typical applications, and treat operations like AddPortMapping as high-risk functions needing additional checks.
- Add policy-based controls: Implement allowlists for which LAN clients or applications may request port mappings, or restrict the ranges and protocols that can be opened.
- Surface changes to users and admins: Log and optionally notify about dynamic port mappings and WAN configuration queries so that abnormal behavior can be identified quickly.
- Network segmentation: Place guest or less-trusted devices on separate segments or SSIDs that do not have access to the router's UPnP control interface.
How teams detect issues like this
Detection can be approached at both configuration and traffic levels.
Possible strategies include:
- Configuration review: Periodically audit router and controller configurations to ensure UPnP is disabled where not strictly needed, and that any UPnP security options are set to restrictive modes.
- Static and firmware analysis: For product security teams, inspect firmware and UPnP daemon code/configs for missing authentication checks on IGD actions such as AddPortMapping, DeletePortMapping, and GetExternalIPAddress.
- Network monitoring: Use IDS/IPS or network monitoring tools to detect unusual or frequent UPnP control messages from non-standard endpoints (e.g., IoT or guest devices) attempting to open ports.
- Log correlation and alerting: Where routers expose logs of UPnP activity, track new or modified port mappings and correlate them with the originating device to flag suspicious changes.
- Policy enforcement in managed environments: Employ NAC (Network Access Control) and router/firewall policies that restrict which hosts may send UPnP control traffic or access port 1900.

