CVE-2013-7183
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 · uneditedcgi-bin/reboot.cgi on Seowon Intech SWC-9100 routers allows remote attackers to (1) cause a denial of service (reboot) via a default_reboot action or (2) reset all configuration values via a factory_default action.
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 · moderate confidenceThe Seowon Intech SWC-9100 router contains an unauthenticated command execution vulnerability in the cgi-bin/reboot.cgi script. Remote attackers can trigger device reboot or factory reset by sending requests with the default_reboot or factory_default action parameters, causing denial of service or complete configuration loss.
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 dataall versionsCVSS 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
- Adjacent
- Complexity
- Low
- Authentication
- None
- Confidentiality
- None
- Integrity
- Complete
- Availability
- Complete
AV:A/AC:L/Au:N/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the device modelCheck the router's web interface login page, label, or SNMP sysDescr for 'Seowonintech' or 'SWC-9100' identificationAffected if The device is a Seowon Intech SWC-9100 router
-
Confirm the firmware versionAccess the router's admin panel or check the system info page for the firmware version; note that all versions are affectedAffected if The device is running any firmware version of the SWC-9100
-
Verify cgi-bin/reboot.cgi is accessibleSend an HTTP GET or POST request to http://<router-ip>/cgi-bin/reboot.cgi and check for a responseAffected if The reboot.cgi endpoint responds (indicates the vulnerable script is present)
-
Check if remote management is enabledInspect the router's web management settings for 'Remote Management', 'Remote Access', or 'WAN Access' configuration; verify if the web interface is bound to WAN IP or exposed externallyAffected if Remote management/WAN access to the web interface is enabled and the device is accessible from untrusted networks
You are affected if you have a Seowon Intech SWC-9100 router with its web management interface (specifically the cgi-bin/reboot.cgi script) accessible, particularly if remote WAN management is enabled, as unauthenticated attackers can trigger reboots or factory resets via the default_reboot or factory_default parameters.
Generated from the published advisory. Verify against your own configuration.
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.
From vendor dataImmediately restrict external WAN access to the router's web management interface via firewall rules or disable remote management. If available, apply vendor firmware updates; otherwise, implement network segmentation to isolate the device from untrusted networks.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2013-7183 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2013-7183 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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