CVE-2005-2799

HIGHCVSS v2 · 7.57.5—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 7.5 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:L/Au:N/C:P/I:P/A:P. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 70.8% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
7.5EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 71%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 71%CVSS v2: 7.5Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Buffer overflow in apply.cgi in Linksys WRT54G 3.01.03, 3.03.6, and possibly other versions before 4.20.7, allows remote attackers to execute arbitrary code via a long HTTP POST request.

CVSS v2.0 (legacy)
7.5HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
7.5(low)
EG Risk
67(Track)
EG Risk 67/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity75% × 45%
Exploitation71% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
71%
EPSS %ILE
99%
KEV
Not listed

Published

September 15, 2005

Last Modified

April 16, 2026

References (2)

Data Freshness Timeline

(refreshed 1× in last 7d / 1× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-09-10 09:23 UTCEPSS rescore
  2. 2026-07-26 13:26 UTCEG score recompute▲ 7.50
  3. 2026-07-25 14:11 UTCEPSS rescore
  4. 2026-07-24 14:11 UTCEPSS rescore
  5. 2026-07-23 00:48 UTCEG score recompute
  6. 2026-07-23 00:28 UTCEG score recompute▼ 6.70
  7. 2026-07-22 23:52 UTCEG score recompute▲ 6.70
  8. 2026-07-22 21:32 UTCEG score recompute▼ 9.00
  9. 2026-07-15 16:53 UTCEPSS rescore
  10. 2026-07-13 06:07 UTCEPSS rescore
  11. 2026-07-13 06:07 UTCEPSS rescore
  12. 2026-07-11 08:22 UTCEPSS rescore
  13. 2026-07-11 08:22 UTCEPSS rescore
  14. 2026-07-08 15:09 UTCEPSS rescore
  15. 2026-07-02 14:00 UTCEPSS rescore
  16. 2026-07-01 15:01 UTCEPSS rescore
  17. 2026-06-29 14:02 UTCEPSS rescore
  18. 2026-06-29 14:02 UTCEPSS rescore
  19. 2026-06-27 03:04 UTCEPSS rescore
  20. 2026-06-25 13:46 UTCEPSS rescore
  21. 2026-06-24 14:01 UTCEPSS rescore
  22. 2026-06-23 21:29 UTCEPSS rescore
  23. 2026-06-18 17:49 UTCEPSS rescore
  24. 2026-06-18 17:49 UTCEPSS rescore
  25. 2026-06-17 17:49 UTCEPSS rescore
Show 31 more
  1. 2026-06-17 17:49 UTCEPSS rescore
  2. 2026-06-16 17:49 UTCEPSS rescore
  3. 2026-06-16 17:49 UTCEPSS rescore
  4. 2026-06-15 17:44 UTCEPSS rescore
  5. 2026-06-14 23:13 UTCEPSS rescore
  6. 2026-06-14 23:13 UTCEPSS rescore
  7. 2026-06-13 22:56 UTCEPSS rescore
  8. 2026-06-12 23:08 UTCEPSS rescore
  9. 2026-06-11 13:55 UTCEPSS rescore
  10. 2026-06-10 22:14 UTCEPSS rescore
  11. 2026-06-10 13:17 UTCEPSS rescore
  12. 2026-06-05 22:43 UTCEPSS rescore
  13. 2026-06-05 22:43 UTCEPSS rescore
  14. 2026-06-04 13:09 UTCEPSS rescore
  15. 2026-06-04 13:09 UTCEPSS rescore
  16. 2026-06-02 20:10 UTCEPSS rescore
  17. 2026-06-02 20:10 UTCEPSS rescore
  18. 2026-06-01 13:49 UTCEPSS rescore
  19. 2026-06-01 13:49 UTCEPSS rescore
  20. 2026-05-31 22:28 UTCEPSS rescore
  21. 2026-05-31 12:11 UTCEG score recompute
  22. 2026-05-31 12:11 UTCGHSA enrichment
  23. 2026-05-29 13:40 UTCEPSS rescore
  24. 2026-05-29 13:40 UTCEPSS rescore
  25. 2026-05-28 13:42 UTCEPSS rescore
  26. 2026-05-28 13:42 UTCEPSS rescore
  27. 2026-05-28 13:42 UTCEPSS rescore
  28. 2026-05-27 13:37 UTCEPSS rescore
  29. 2026-05-26 07:16 UTCEPSS rescore
  30. 2026-05-26 07:16 UTCEPSS rescore
  31. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (2 Metasploit modules) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Metasploitexploit/linux/http/linksys_wrt54gl_apply_exec✓ verified
    First seen Jan 18, 2013

    Linksys WRT54GL apply.cgi Command Execution

    Open source ↗
  • Exploit-DBEDB-16854✓ verified
    First seen Sep 24, 2010

    Linksys WRT54 Access Point - 'apply.cgi' Remote Buffer Overflow (Metasploit)

    Open source ↗
  • Exploit-DBEDB-10028✓ verified
    First seen Sep 13, 2005

    Linksys WRT54G < 4.20.7 / WRT54GS < 1.05.2 - 'apply.cgi' Remote Buffer Overflow (Metasploit)

    Open source ↗
  • Metasploitexploit/linux/http/linksys_apply_cgi✓ verified
    First seen Sep 13, 2005

    Linksys WRT54 Access Point apply.cgi Buffer Overflow

    Open source ↗

Frequently asked(4)

What is CVE-2005-2799?
CVE-2005-2799 is a high vulnerability published on September 15, 2005. Buffer overflow in apply.cgi in Linksys WRT54G 3.01.03, 3.03.6, and possibly other versions before 4.20.7, allows remote attackers to execute arbitrary code via a long HTTP POST request.
When was CVE-2005-2799 disclosed?
CVE-2005-2799 was first published in the National Vulnerability Database on September 15, 2005, with the most recent update on April 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2005-2799 actively exploited?
CVE-2005-2799 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 71% probability of exploitation in the next 30 days, which ranks it in the top 0.6% of all scored CVEs.
How do I remediate CVE-2005-2799?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2005-2799, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2005-2799

Explore →

Is Your Infrastructure Affected by CVE-2005-2799?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs