dbcve.org
Iologik E1200 Series FirmwareOperating system · Moxa

CVE-2016-8359

MEDIUM · 6.1 CVSS v3.1 Published 2017-02-13
Fix available
A fix is available. Upgrade to after 3.13 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
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).

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 confidence

Moxa ioLogik E1200 and E2200 series industrial IoT devices contain a stored Cross-Site Scripting (XSS) vulnerability in their web interface. The web application fails to properly sanitize user input, allowing authenticated attackers to inject malicious JavaScript or HTML into web pages served by the device, potentially leading to session hijacking or execution of arbitrary code in the context of other users viewing the compromised interface.

MitigationUpdate firmware to vendor-specified patched versions (V2.5+ for E1200 series, V3.12-V3.14+ for E2200 series depending on model). If immediate patching is not feasible, restrict network access to the web management interface and implement WAF rules to filter malicious input.

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
Iologik E1200 Series FirmwareOperating system
Affected:<= 2.4<= 2.3<= 2.5
Iologik E2200 Series FirmwareOperating system
Affected:<= 3.11<= 3.12<= 3.13

CVSS 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
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify device model
    Access the device web interface or check the physical device labeling to confirm it is an E1200 or E2200 series ioLogik device
    Affected if Device is an E1200 or E2200 series model
  2. Check firmware version on E1200 series
    Log into the web interface and navigate to System Settings or About page to view the firmware version. Compare against vulnerable versions: 2.3, 2.4, 2.5 or earlier
    Affected if Firmware version is 2.5 or lower (2.3, 2.4, 2.5)
  3. Check firmware version on E2200 series
    Log into the web interface and navigate to System Settings or About page to view the firmware version. Compare against vulnerable versions: 3.11, 3.12, 3.13 or earlier
    Affected if Firmware version is 3.13 or lower (3.11, 3.12, 3.13)
  4. Confirm web interface is enabled
    Attempt to access the device web interface via HTTP/HTTPS in a browser
    Affected if Web interface is accessible and authentication is possible (required for XSS injection)

You are affected if you have an E1200 series device with firmware 2.5 or lower, or an E2200 series device with firmware 3.13 or lower, and the web management interface is enabled.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 3.13
Interim mitigation

Update firmware to vendor-specified patched versions (V2.5+ for E1200 series, V3.12-V3.14+ for E2200 series depending on model). If immediate patching is not feasible, restrict network access to the web management interface and implement WAF rules to filter malicious input.

Fix this in Iologik E1200 Series Firmware Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-8359 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-8359 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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