dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2013-3307

HIGH · 8.3 CVSS v3.1 Published 2025-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
92/100
Remediation priority · Urgent
High EPSS 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 E1000 devices through 2.1.02, E1200 devices before 2.0.05, and E3200 devices through 1.0.04 allow OS command injection via shell metacharacters in the apply.cgi ping_ip parameter on TCP port 52000.

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

OS command injection vulnerability in Linksys E1000, E1200, and E3200 routers allows remote attackers to execute arbitrary commands via shell metacharacters in the ping_ip parameter of apply.cgi on TCP port 52000. The web interface fails to properly sanitize user input before passing it to system shell commands.

MitigationReplace affected end-of-life routers or apply vendor firmware updates if available; network segmentation can reduce exposure until replacement.

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

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
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

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 router model
    Access the router web interface or check the device label/metadata to confirm the model number is E1000, E1200, or E3200
    Affected if Model is E1000, E1200, or E3200 (any firmware version)
  2. Verify web interface port is accessible
    Attempt to connect to the router on TCP port 52000 (e.g., curl http://router-ip:52000 or telnet/nc router-ip 52000)
    Affected if Port 52000 is open and responds to HTTP requests
  3. Check apply.cgi ping endpoint
    Send a request to apply.cgi with the ping_ip parameter (e.g., http://router-ip:52000/apply.cgi?ping_ip=1.1.1.1) and observe if the ping parameter is processed
    Affected if The apply.cgi responds and appears to process the ping_ip parameter
  4. Confirm lack of input sanitization
    Send a test request with shell metacharacters in ping_ip (e.g., ping_ip=;echo test) and check if command injection occurs or characters are not filtered
    Affected if Shell metacharacters are accepted without sanitization or error
  5. Check firmware version
    If accessible, check the router firmware version in the web interface or via SNMP/UPnP
    Affected if Firmware is any version on these affected models (no fixed version confirmed in provided data)

The environment is affected if it is a Linksys E1000, E1200, or E3200 router with the web interface accessible on port 52000 and the apply.cgi ping functionality exposed without input sanitization.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Replace affected end-of-life routers or apply vendor firmware updates if available; network segmentation can reduce exposure until replacement.

Recommended fix Moderate confidence

Linksys E-series firmware 2.0.05 or later (E1200), or latest available firmware beyond 2.1.02 (E1000) and 1.0.04 (E3200)

  1. 1. Identify the exact model number and current firmware version of the Linksys device (E1000, E1200, or E3200)
  2. 2. Check Linksys support site (support.linksys.com) for available firmware updates for the specific model
  3. 3. If firmware version 2.0.05 or later is available for E1200, or a version later than 2.1.02 for E1000, or later than 1.0.04 for E3200, download and apply the update
  4. 4. After updating, verify the apply.cgi interface no longer accepts shell metacharacters in the ping_ip parameter
  5. 5. If no firmware update is available from Linksys, strongly consider replacing the device with a newer model that still receives security updates
Caveat Firmware updates for older consumer routers may reset configuration to defaults; backup current settings before applying update

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

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2013-3307 — 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-2013-3307 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