CVE-2023-39780

KEVASUS RT-AX55 Routers OS Command Injection Vulnerability

Description

ASUS RT-AX55 devices contain an OS command injection vulnerability that could allow a remote, authenticated attacker to execute arbitrary commands. As represented by CVE-2023-41346.

On ASUS RT-AX55 3.0.0.4.386.51598 devices, authenticated attackers can perform OS command injection via the /start_apply.htm qos_bw_rulelist parameter. NOTE: for the similar "token-generated module" issue, see CVE-2023-41345; for the similar "token-refresh module" issue, see CVE-2023-41346; for the similar "check token module" issue, see CVE-2023-41347; and for the similar "code-authentication module" issue, see CVE-2023-41348.

CVSS 3.1 vectorCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

PublishedSep 11, 2023

Last modifiedJun 17, 2026

Added to KEVJun 2, 2025

Remediation dueJun 23, 2025

References

github.com/D2y6p/CVE/blob/main/asus/CVE-2023-39780/1/EN.mdExploitThird Party Advisory
github.com/D2y6p/CVE/blob/main/asus/CVE-2023-39780/2/EN.mdExploitThird Party Advisory
github.com/D2y6p/CVE/blob/main/asus/CVE-2023-39780/3/EN.mdExploitThird Party Advisory
github.com/D2y6p/CVE/blob/main/asus/CVE-2023-39780/4/EN.mdExploitThird Party Advisory
github.com/D2y6p/CVE/blob/main/asus/CVE-2023-39780/5/EN.mdExploitThird Party Advisory
github.com/D2y6p/CVE/blob/main/asus/CVE-2023-39780/6/EN.mdExploitThird Party Advisory
cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-39780US Government Resource
greynoise.io/blog/stealthy-backdoor-campaign-affecting-asus-routersExploitThird Party Advisory

0 recent articles mention this CVE

Risk assessment · High

Actively exploited. Patch immediately.

Exploitation: Confirmed in the wild (CISA KEV)
Federal remediation deadline: Overdue by 491 days
CVSS: 8.8 HIGH
EPSS (30-day exploit probability): 39.5% · top 1% of all CVEs
Weakness: CWE-78
Attack vector: Network, remotely reachable

Recommended actions

1.Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
2.Treat as emergency change: patch or isolate internet-facing instances first.
3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.

Assessment is derived automatically from the live signals above; verify against your own asset inventory.