CVE-2016-5805
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 in Delta Electronics WPLSoft, Versions prior to V2.42.11, ISPSoft, Versions prior to 3.02.11, and PMSoft, Versions prior to2.10.10. There are multiple instances of heap-based buffer overflows that may allow malicious files to cause the execution of arbitrary code or a denial of service.
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 confidenceHeap-based buffer overflow vulnerabilities exist in Delta Electronics WPLSoft, ISPSoft, and PMSoft when processing malicious files. These flaws can be exploited to achieve arbitrary code execution or cause a denial of service on affected systems.
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 versionsall versionsall 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/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 installed Delta Electronics softwareCheck system for presence of WPLSoft, ISPSoft, or PMSoft executables or installed programs. Look in common installation directories (typically C:\Delta\ or Program Files\) or use system inventory tools to list installed software.Affected if Any of these three Delta Electronics applications are found on the system
-
Determine installed version of WPLSoftOpen WPLSoft and navigate to Help > About, or right-click the executable and view Properties > Details for version information. Alternatively, locate the WPLSoft.exe file and check its version property.Affected if Version is lower than 2.42.11 (all versions below this are affected)
-
Determine installed version of ISPSoftOpen ISPSoft and navigate to Help > About, or right-click the executable and view Properties > Details. Check the version information displayed.Affected if Version is lower than 3.02.11 (all versions below this are affected)
-
Determine installed version of PMSoftOpen PMSoft and navigate to Help > About, or right-click the executable and view Properties > Details for version information.Affected if Version is lower than 2.10.10 (all versions below this are affected)
The system is affected if any of these three Delta Electronics applications (WPLSoft, ISPSoft, or PMSoft) are installed with versions below their respective patched releases (2.42.11, 3.02.11, and 2.10.10).
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 dataUpdate to vendor-patched versions: WPLSoft V2.42.11 or later, ISPSoft V3.02.11 or later, PMSoft V2.10.10 or later. Verify compatibility in test environment before production deployment.
- Consultation2.0 h
- Implementation4.0 h
- Testing8.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 $4,288.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5805 — 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-2016-5805 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