CVE-2016-8360
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 Moxa SoftCMS versions prior to Version 1.6. A specially crafted URL request sent to the SoftCMS ASP Webserver can cause a double free condition on the server allowing an attacker to modify memory locations and possibly cause a denial of service or the execution of arbitrary code.
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 confidenceMoxa SoftCMS versions prior to 1.6 contain a double-free vulnerability in the ASP Webserver component. Attackers can trigger this by sending specially crafted URL requests, causing memory corruption that may lead to denial of service or arbitrary code execution.
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<= 1.5CVSS 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
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:H/PR:N/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 installed SoftCMS versionLocate the Moxa SoftCMS installation directory and check the version information in the software's main executable, about dialog, or version file. Common locations include the program files folder or the installation root. Run 'Moxa SoftCMS' and access the Help > About section if a GUI is available.Affected if The installed version is 1.5 or lower (any version prior to 1.6)
-
Confirm ASP Webserver component is activeCheck if the SoftCMS web server service is running. On Windows, open Services.msc and look for 'Moxa SoftCMS' or check the task manager for related processes. The vulnerability exists in the ASP Webserver component specifically.Affected if The SoftCMS web server service is running and responding to HTTP requests
-
Verify web server network exposureCheck which network interfaces the SoftCMS web server is bound to. Use 'netstat -an | grep [port]' where [port] is typically 8080 or 80 for web servers. Inspect the server configuration files for binding addresses.Affected if The web server is accessible on network interfaces beyond localhost (0.0.0.0 or external IP addresses)
-
Review access logs for suspicious URL patternsExamine the SoftCMS web server access logs for unusual or malformed URL requests. Look for patterns that might indicate exploitation attempts, such as encoded characters, buffer overflow attempts, or repeated requests with unusual parameters.Affected if Logs show requests with suspicious URL patterns that could indicate exploitation attempts
You are affected if SoftCMS version 1.5 or lower is installed AND the ASP web server component is running and accessible.
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 dataUpgrade Moxa SoftCMS to version 1.6 or later. If upgrading is not immediately feasible, restrict network access to the web server and monitor for suspicious URL patterns.
- Consultation4.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,736.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-8360 — 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-8360 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