CVE-2017-12573
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 · uneditedAn issue was discovered on PLANEX CS-W50HD devices with firmware before 030720. The device has a command-injection vulnerability in the web management UI on NAS settings page "/cgi-bin/nasset.cgi". An attacker can send a crafted HTTP POST request to execute arbitrary code. Authentication is required before executing the attack.
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 confidenceAuthenticated command injection vulnerability in PLANEX CS-W50HD NAS devices. The web management interface at /cgi-bin/nasset.cgi fails to properly sanitize user input in NAS settings, allowing authenticated attackers to inject arbitrary OS commands via crafted HTTP POST requests.
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< 030720CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 modelAccess the device's web interface or check the product label/menu to confirm the model is PLANEX CS-W50HD NASAffected if The device is not a PLANEX CS-W50HD NAS - different models are not affected by this specific vulnerability
-
Check the firmware versionLog into the web management interface and navigate to System Settings or Status to view the firmware version, or check via CLI if availableAffected if The firmware version is lower than 030720 (e.g., 020100, 020900, etc.) - versions below 030720 are affected
-
Verify web interface accessibilityAttempt to access http://[device-ip]/cgi-bin/nasset.cgi via browser or curl to confirm the management interface is reachableAffected if The /cgi-bin/nasset.cgi endpoint is accessible from an untrusted network - this is the vulnerable component
-
Confirm authentication is requiredTry accessing the web interface without credentials to see if login is enforced, or check if default credentials are still in useAffected if The web interface is accessible without proper authentication or uses default credentials - this enables the authenticated attack vector
-
Check network exposureDetermine if the device's admin interface is exposed to the internet or untrusted networks by reviewing firewall rules or port forwarding configurationsAffected if The management interface is exposed to the internet or untrusted networks - this increases exploitability but authentication is still required
A user is affected if they have a PLANEX CS-W50HD NAS running firmware version below 030720 with the web management interface accessible to an authenticated attacker.
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 data030720
Update firmware to version 030720 or later. If updates unavailable, restrict administrative interface access to trusted networks only and ensure strong, unique credentials.
- Consultation2.0 h
- Implementation6.0 h
- Testing4.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,904.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12573 — 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-2017-12573 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