CVE-2016-9333
CVE-2016-9333 is a critical-severity vulnerability in Moxa Softcms with a CVSS 3.x base score of 9.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-89.
Key facts
- Severity: Critical (CVSS 3.x base score 9.8)
- CVSS v2: 7.5
- EPSS exploit prediction: 2% (80th percentile)
- Actively exploited: Not listed in CISA KEV
- Weakness: CWE-89
- Affected product: Moxa Softcms
- Published:
- Last modified:
Description
An issue was discovered in Moxa SoftCMS versions prior to Version 1.6. The SoftCMS Application does not properly sanitize input that may allow a remote attacker access to SoftCMS with administrator's privilege through specially crafted input (SQL INJECTION).
Frequently asked questions
- What is CVE-2016-9333?
- An issue was discovered in Moxa SoftCMS versions prior to Version 1.6. The SoftCMS Application does not properly sanitize input that may allow a remote attacker access to SoftCMS with administrator's privilege through specially crafted input (SQL INJECTION).
- How severe is CVE-2016-9333?
- CVE-2016-9333 has a CVSS 3.x base score of 9.8, rated critical severity. It is exploitable over network with low attack complexity, requires no privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
- Is CVE-2016-9333 being actively exploited?
- It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 2% (80th percentile), an estimate of the probability of exploitation in the next 30 days.
- What products are affected by CVE-2016-9333?
- CVE-2016-9333 affects Moxa Softcms. See the affected-products list for the exact vulnerable versions.
- How do I fix CVE-2016-9333?
- Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its critical severity, prioritise patching exposed systems.
- When was CVE-2016-9333 published?
- CVE-2016-9333 was published on 2017-02-13 and last updated on 2026-06-17.
References
Affected products (1)
- cpe:2.3:a:moxa:softcms:*:*:*:*:*:*:*:*
More vulnerabilities in Moxa Softcms
- CVE-2016-5792 — Critical (CVSS 9.8): SQL injection vulnerability in Moxa SoftCMS before 1.5 allows remote attackers to execute arbitrary SQL commands via…
- CVE-2015-6458 — High (CVSS 8.8): Moxa SoftCMS 1.3 and prior is susceptible to a buffer overflow condition that may crash or allow remote code execution.…
- CVE-2015-6457 — High (CVSS 8.8): Moxa SoftCMS 1.3 and prior is susceptible to a buffer overflow condition that may crash or allow remote code execution.…
- CVE-2016-8360 — High (CVSS 8.1): An issue was discovered in Moxa SoftCMS versions prior to Version 1.6. A specially crafted URL request sent to the…
- CVE-2016-9332 — High (CVSS 7.5): An issue was discovered in Moxa SoftCMS versions prior to Version 1.6. Moxa SoftCMS Webserver does not properly…
- CVE-2015-1000 — Medium (CVSS 6.8): Stack-based buffer overflow in the OpenForIPCamTest method in the RTSPVIDEO.rtspvideoCtrl.1 (aka SStreamVideo) ActiveX…
All CVEs affecting Moxa Softcms →
Other CWE-89 (SQL Injection) vulnerabilities
- CVE-2026-124815 — Critical (CVSS 10.0): The Clockinator Lite WordPress plugin before 1.1.0 does not restrict access to several of its record deletion actions,…
- CVE-2026-105781 — Critical (CVSS 10.0): Adobe Campaign Classic (ACC) is affected by an Improper Neutralization of Special Elements used in an SQL Command ('SQL…
- CVE-2026-79849 — Critical (CVSS 10.0): Vulnerabilities in the affected interface of AOS-8 could allow an unauthenticated remote attacker to conduct SQL…
- CVE-2026-79848 — Critical (CVSS 10.0): Vulnerabilities in the affected interface of AOS-8 could allow an unauthenticated remote attacker to conduct SQL…
- CVE-2026-55572 — Critical (CVSS 10.0): e107 is a content management system (CMS). Prior to 2.3.7, the bundled alt_auth plugin's otherdb and e107db…
- CVE-2026-12260 — Critical (CVSS 10.0): SQL injection in the NetBoard CRM demo platform; specifically, the vulnerable component is the ‘user-name’ POST…