# CVE-2016-9332: An issue was discovered in Moxa SoftCMS versions prior to Version 1.6.


- **Severity:** High 7.5 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 13 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-55xr-gqp7-q7ff

## What is CVE-2016-9332?

CVE-2016-9332 is a high-severity vulnerability in Moxa SoftCMS prior to Version 1.6, published on 13 Feb 2017. 

### Official description

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.

Weakness: CWE-399

## Which versions are affected by CVE-2016-9332?

It affects 1 product.


Products: Moxa Softcms.

## How do I fix CVE-2016-9332?

No fix has been published for CVE-2016-9332 yet. Limit exposure of the affected software until one is available.

## Is CVE-2016-9332 being exploited?

There is no known exploitation of CVE-2016-9332 in the wild and no public exploit code.

Public exploit code:

- Moxa SoftCMS 1.5 - Denial of Service (PoC) (exploitdb)

## Other vulnerabilities in Moxa SoftCMS prior to Version 1.6

- [CVE-2016-9333](https://insights.sbomify.com/CVE-2016-9333/): SQL injection in Moxa SoftCMS prior to Version 1.6 (critical 9.8)
- [CVE-2016-5792](https://insights.sbomify.com/CVE-2016-5792/): SQL injection in n/a (critical 9.8)
- [CVE-2015-6457](https://insights.sbomify.com/CVE-2015-6457/): Memory corruption in SoftCMS (high 8.8)
- [CVE-2015-6458](https://insights.sbomify.com/CVE-2015-6458/): Memory corruption in SoftCMS (high 8.8)
- [CVE-2016-8360](https://insights.sbomify.com/CVE-2016-8360/): Use after free in Moxa SoftCMS prior to Version 1.6 (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2016-9332 and fix it if it is affected.

What it is: CVE-2016-9332 is a high-severity vulnerability in Moxa SoftCMS prior to Version 1.6, published on 13 Feb 2017. 
Exploitation: There is no known exploitation of CVE-2016-9332 in the wild and no public exploit code.

Affected product: Moxa SoftCMS prior to Version 1.6. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2016-9332/ (Markdown: https://insights.sbomify.com/CVE-2016-9332/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2016-9332
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2016-9332
- OSV: https://osv.dev/vulnerability/CVE-2016-9332

---
From sbomify Insights: https://insights.sbomify.com/CVE-2016-9332/
Summaries are generated and may contain mistakes; the official description above is the record.