Skip to content
vulnerability

CVE-2023-39780

8.8
High
KEV · Exploited in wildEPSS 40%

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.

exploited
Yes, in CISA KEV since 2 Jun 2025fix by 23 Jun 2025 (CISA deadline for US federal agencies)unvetted proof-of-concept code on github
fix
No fixed release stated by the publisher
likelihood
EPSS 39.5%
Published 11 Sept 2023Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

triage
server-sideruntimeWAF can block: partlyAV · networkCWE-78· OS Command Injection

Can a WAF block it? Partly. OS command injection puts shell syntax into the request. WAF rules catch common shell commands but miss encoded or unusual payloads.

Also consider: shlex/execve-style APIs

Based on the weakness type only; no CVE-specific evidence yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requiredlowuser interactionnonescopeunchangedconfidentialityhighintegrityhighavailabilityhigh
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
common questions

Is CVE-2023-39780 being exploited?

Yes. CVE-2023-39780 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2023-39780?

CVE-2023-39780 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2023-39780?

Not known from our data. No patch reference has been recorded for CVE-2023-39780, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.

What does CVE-2023-39780 affect?

CVE-2023-39780 affects asus:rt-ax55_firmware. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
asus:rt-ax55_firmware
affected versions
ASUS RT-AX55
  • affected3.0.0.4.386.51598

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Unvetted proof-of-concept code on GitHub: 1 GitHub proof of concept

GitHub proofs of concept

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
no
technical impact
total

Assessed by CISA 6 Jun 2025 (SSVC 2.0.3).

timeline

  1. 11 Sept 2023Published
  2. 2 Jun 2025Added to CISA KEV (exploited in the wild) · 629 days (about 2 years) later
  3. 6 Jun 2025CISA SSVC assessment: exploitation active · 4 days later
  4. 23 Jun 2025CISA remediation due date (US federal agencies) · 17 days later
  5. 21 Oct 2025CVE record last updated · 121 days (about 4 months) later
  6. 30 Oct 2026First proof-of-concept repository on GitHub (unvetted) · 373 days (about 1 year) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 4 days later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
NVDCVE.orgCVE DetailsSource
8 references in the CVE record: 8 links
  • Linkgithub.com /D2y6p/CVE/blob/main/asus/CVE-2023-39780/1/EN.md
  • Linkgithub.com /D2y6p/CVE/blob/main/asus/CVE-2023-39780/2/EN.md
  • Linkgithub.com /D2y6p/CVE/blob/main/asus/CVE-2023-39780/3/EN.md
  • Linkgithub.com /D2y6p/CVE/blob/main/asus/CVE-2023-39780/4/EN.md
  • Linkgithub.com /D2y6p/CVE/blob/main/asus/CVE-2023-39780/5/EN.md
  • Linkgithub.com /D2y6p/CVE/blob/main/asus/CVE-2023-39780/6/EN.md
  • Linkgreynoise.io /blog/stealthy-backdoor-campaign-affecting-asus-routers
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2023-39780

sources

  • CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
  • NVD: CVSS and CPE data
  • CISA KEV catalog: exploitation, date added, due date
  • CISA Vulnrichment (ADP): SSVC decision points
  • FIRST EPSS: exploit probability and percentile
  • PoC-in-GitHub: GitHub repositories that claim a proof of concept
  • Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved