Skip to content
Fencer Intel
critical 9.8

CVE-2018-5999 in the critical feed json

An issue was discovered in AsusWRT before 3.0.0.4.384_10007.

published 8y ago modified 4mo ago also EUVD-2018-17764

cvss
9.8
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
87.5%
EPSS 87.5% chance of exploitation in 30 days, percentile 99.7%
public exploits
3
Metasploit and Exploit-DB

Summary

An issue was discovered in AsusWRT before 3.0.0.4.384_10007. In the handle_request function in router/httpd/httpd.c, processing of POST requests continues even if authentication fails.

Patch / fix

  • asus asuswrt 3.0.0.4.384_10007

Is CVE-2018-5999 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. First public exploit (Metasploit exploit/linux/http/asuswrt_lan_rce)
  2. Published

Exploit prediction

87.53% chance of exploitation in the next 30 days, higher than 99.7% of all scored CVEs (FIRST EPSS, 2026-11-09).

Exploits and checks

  • Metasploit exploit/linux/http/asuswrt_lan_rce AsusWRT LAN Unauthenticated Remote Code Execution metasploit exploit, excellent rank, 2018-01-22
  • EDB-44176 AsusWRT LAN - Remote Code Execution (Metasploit) remote, 2018-02-26
  • EDB-43881 AsusWRT Router < 3.0.0.4.380.7743 - LAN Remote Code Execution remote, 2018-01-22
  • github.com https://github.com/pedrib/PoC/blob/master/advisories/asuswrt-lan-rce.txt referenced PoC, tagged "exploit" by a source, unverified
  • blogs.securiteam.com https://blogs.securiteam.com/index.php/archives/3589 referenced PoC, tagged "exploit" by a source, unverified
  • raw.githubusercontent.com https://raw.githubusercontent.com/pedrib/PoC/master/exploits/metasploit/asuswrt_lan_rce.rb referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 3.0 9.8 CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
NVD 2.0 10.0 AV:N/AC:L/Au:N/C:C/I:C/A:C

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.