CVE-2010-1573 in the critical feed json
Linksys WAP54Gv3 firmware 3.04.03 and earlier uses a hard-coded username (Gemtek) and password (gemtekswd) for a debug interface for certai…
published 16y ago modified 4mo ago also EUVD-2010-1600
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 20.8%
- EPSS 20.8% chance of exploitation in 30 days, percentile 97%
- public exploits
- 0
- none known
Summary
Linksys WAP54Gv3 firmware 3.04.03 and earlier uses a hard-coded username (Gemtek) and password (gemtekswd) for a debug interface for certain web pages, which allows remote attackers to execute arbitrary commands via the (1) data1, (2) data2, or (3) data3 parameters to (a) Debug_command_page.asp and (b) debug.cgi.
Is CVE-2010-1573 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 FencerExploit prediction
20.79% chance of exploitation in the next 30 days, higher than 97% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- icysilence.org http://www.icysilence.org/?p=268 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/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 |
Classification
- Weakness
-
- CWE-798 Use of Hard-coded Credentials
References
-
icysilence.org
/?p=268
exploit
-
tools.cisco.com
/security/center/viewAlert.x?alertId=20682
broken-link, vendor-advisory
-
vupen.com
/english/advisories/2010/1419
vdb-entry, broken-link
-
securityfocus.com
/bid/40648
vdb-entry, broken-link, third-party-advisory
-
secunia.com
/advisories/40103
third-party-advisory, broken-link
-
securityfocus.com
/archive/1/511733/100/0/threaded
mailing-list, broken-link, third-party-advisory, vdb-entry
-
exchange.xforce.ibmcloud.com
/vulnerabilities/59286
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2010-1573
- NVD CVE-2010-1573
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.