# CVE-2016-8359: Cross-site scripting in Moxa ioLogik E1200 Series before 3.12

> Attackers can inject scripts or execute arbitrary code via unsanitized input in the web interface of Moxa ioLogik devices.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 13 Feb 2017
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-q25p-m8w9-6f3c

## What is CVE-2016-8359?

CVE-2016-8359 is a medium-severity cross-site scripting vulnerability in Moxa ioLogik E1200 Series before 3.12, published on 13 Feb 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

An issue was discovered in Moxa ioLogik E1210, firmware Version V2.4 and prior, ioLogik E1211, firmware Version V2.3 and prior, ioLogik E1212, firmware Version V2.4 and prior, ioLogik E1213, firmware Version V2.5 and prior, ioLogik E1214, firmware Version V2.4 and prior, ioLogik E1240, firmware Version V2.3 and prior, ioLogik E1241, firmware Version V2.4 and prior, ioLogik E1242, firmware Version V2.4 and prior, ioLogik E1260, firmware Version V2.4 and prior, ioLogik E1262, firmware Version V2.4 and prior, ioLogik E2210, firmware versions prior to V3.13, ioLogik E2212, firmware versions prior to V3.14, ioLogik E2214, firmware versions prior to V3.12, ioLogik E2240, firmware versions prior to V3.12, ioLogik E2242, firmware versions prior to V3.12, ioLogik E2260, firmware versions prior to V3.13, and ioLogik E2262, firmware versions prior to V3.12. The web application fails to sanitize user input, which may allow an attacker to inject script or execute arbitrary code (CROSS-SITE SCRIPTING).

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 2 products.


Products: Moxa Iologik E1200 Series Firmware, Moxa Iologik E2200 Series Firmware.

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

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

## Is CVE-2016-8359 being exploited?

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

## Other vulnerabilities in Moxa ioLogik E1200 Series before 3.12

- [CVE-2016-8372](https://insights.sbomify.com/CVE-2016-8372/): Weak cryptography in Moxa ioLogik E1200 Series before 3.12 (high 8.1)
- [CVE-2016-8379](https://insights.sbomify.com/CVE-2016-8379/): Weak cryptography in Moxa ioLogik E1200 Series before 3.12 (high 8.1)
- [CVE-2016-8350](https://insights.sbomify.com/CVE-2016-8350/): Cross-site request forgery in Moxa ioLogik E1200 Series before 3.12 (medium 6.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2016-8359 is a medium-severity cross-site scripting vulnerability in Moxa ioLogik E1200 Series before 3.12, published on 13 Feb 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2016-8359 in the wild and no public exploit code.

Affected product: Moxa ioLogik E1200 Series before 3.12. 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-8359/ (Markdown: https://insights.sbomify.com/CVE-2016-8359/index.md)
```

## Sources

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

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