dbcve.org
Wap54gv3Hardware / appliance · Linksys

CVE-2010-2261

HIGH · 10.0 CVSS v2.0 Published 2010-06-10
Fix available
A fix is available. Upgrade to after 3.04.03 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Linksys WAP54Gv3 firmware 3.04.03 and earlier allows remote attackers to execute arbitrary commands via shell metacharacters in the (1) data2 and (2) data3 parameters to (a) Debug_command_page.asp and (b) debug.cgi.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Command injection vulnerability in Linksys WAP54Gv3 wireless access point firmware 3.04.03 and earlier. Attackers can execute arbitrary OS commands by including shell metacharacters in the data2 and data3 parameters of Debug_command_page.asp and debug.cgi debug functions.

MitigationSince this is a critical remote code execution flaw in likely end-of-life firmware, the primary remediation is device replacement or network isolation. If the device is still supported, apply available firmware updates; otherwise, segment the device from sensitive networks or retire the hardware.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wap54gv3Hardware / appliance
Affected:<= 3.04.03= 3.05.03

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Log into the web interface or check the device label to confirm it is a Linksys WAP54Gv3 wireless access point
    Affected if The device is a WAP54Gv3 unit
  2. Determine the firmware version
    Access the router web interface, typically at 192.168.1.1, and navigate to the Administration or Status page to view the firmware version string
    Affected if The installed firmware version is 3.04.03 or earlier, or exactly 3.05.03
  3. Check if debug functions are accessible
    Attempt to access the URLs /Debug_command_page.asp or /debug.cgi on the device HTTP server using a browser or curl command
    Affected if The debug pages return a valid response rather than a 404 error, indicating the debug functionality is present and enabled
  4. Verify network exposure
    Determine if the device HTTP management interface is reachable from untrusted networks such as the internet or a guest network segment
    Affected if The device management interface is exposed to networks outside the trusted administrative LAN

The device is affected if it is a Linksys WAP54Gv3 running firmware version 3.04.03 or earlier, or version 3.05.03, and the debug functions are accessible on the network.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.04.03
Interim mitigation

Since this is a critical remote code execution flaw in likely end-of-life firmware, the primary remediation is device replacement or network isolation. If the device is still supported, apply available firmware updates; otherwise, segment the device from sensitive networks or retire the hardware.

Recommended fix High confidence
  1. This is a legacy Linksys WAP54Gv3 router that has been discontinued and no longer receives firmware updates from Cisco/Linksys.
  2. The Debug_command_page.asp and debug.cgi interfaces expose a command injection vulnerability (CWE-94) in both data2 and data3 parameters.
  3. There is no official firmware patch available for this device as it has reached end-of-life.
  4. If this device is still in production, it should be replaced with a currently supported router that receives security updates.
  5. Network segmentation can be applied as a mitigation to limit exposure, but the underlying vulnerability remains unpatched.
  6. If remote access to the debug features is not required, disable or block access to these CGI endpoints at the network perimeter.
Caveat This device is end-of-life with no security patches available; replacement is the only safe option

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Wap54gv3 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2010-2261 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2010-2261 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data