CVE-2006-5202 json
Linksys WRT54g firmware 1.00.9 does not require credentials when making configuration changes, which allows remote attackers to modify arbi…
published 2006-10-09 20 y ago modified 2026-06-16 4 mo ago also EUVD-2006-5187
- cvss
- 5.0
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 4.2%
- EPSS 4.2% chance of exploitation in 30 days, percentile 90%
- public exploits
- 1
- Exploit-DB
Summary
Linksys WRT54g firmware 1.00.9 does not require credentials when making configuration changes, which allows remote attackers to modify arbitrary configurations via a direct request to Security.tri, as demonstrated using the SecurityMode and layout parameters, a different issue than CVE-2006-2559.
Timeline
- Published
- First public exploit (EDB-5926)
Exploit prediction
4.18% chance of exploitation in the next 30 days, higher than 90% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- EDB-5926 Linksys WRT54G Firmware 1.00.9 - Security Bypass (2) remote, 2008-06-24
- securityfocus.com http://www.securityfocus.com/bid/19347 referenced PoC, tagged "exploit" by a source, unverified
- lists.grok.org.uk http://lists.grok.org.uk/pipermail/full-disclosure/2006-August/048495.html referenced PoC, tagged "exploit" by a source, unverified
- securitytracker.com http://securitytracker.com/id?1016638 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 5.0 | AV:N/AC:L/Au:N/C:N/I:P/A:N |
References
-
exploit-db.com
/exploits/5926
exploit
-
securityfocus.com
/bid/19347
vdb-entry, exploit
-
lists.grok.org.uk
/pipermail/full-disclosure/2006-August/048495.html
mailing-list, exploit
-
securitytracker.com
/id?1016638
vdb-entry, exploit
-
secunia.com
/advisories/21372
third-party-advisory, vendor-advisory
- kinqpinz.info /lib/wrt54g/
- kinqpinz.info /lib/wrt54g/own2.txt
-
kb.cert.org
/vuls/id/930364
third-party-advisory, us-government-resource
Sources
- CVE List CVE-2006-5202
- NVD CVE-2006-5202
Fencer Vulns 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.