CVE-2016-9332 json
An issue was discovered in Moxa SoftCMS versions prior to Version 1.6.
published 2017-02-13 9 y ago modified 2026-06-17 4 mo ago also EUVD-2016-10142
- cvss
- 7.5
- version 3.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 8.2%
- EPSS 8.2% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
An issue was discovered in Moxa SoftCMS versions prior to Version 1.6. Moxa SoftCMS Webserver does not properly validate input. An attacker could provide unexpected values and cause the program to crash or excessive consumption of resources could result in a denial-of-service condition.
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
cisa ICSA-16-322-02 updated cvss 7.5
Moxa SoftCMS Vulnerabilities
-
Moxa SoftCMS <1.6affected: mitigation
From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf
Timeline
- First public exploit (EDB-40779)
- Published
Exploit prediction
8.24% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- EDB-40779 Moxa SoftCMS 1.5 - Denial of Service (PoC) dos, 2016-11-18
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.0 | 7.5 | CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H |
| NVD | 2.0 | 7.8 | AV:N/AC:L/Au:N/C:N/I:N/A:C |
Affected products
- n/a Moxa SoftCMS prior to Version 1.6
Classification
- Weakness
-
- CWE-399 Resource Management Errors
References
-
exploit-db.com
/exploits/40779/
exploit
-
ics-cert.us-cert.gov
/advisories/ICSA-16-322-02
mitigation, third-party-advisory, us-government-resource
-
securityfocus.com
/bid/94394
vdb-entry, third-party-advisory
Sources
- CVE List CVE-2016-9332
- NVD CVE-2016-9332
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.