CVE-2016-5819
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 · uneditedMoxa G3100V2 Series, editions prior to Version 2.8, and OnCell G3111/G3151/G3211/G3251 Series, editions prior to Version 1.7 allows a reflected cross-site scripting attack which may allow an attacker to execute arbitrary script code in the user’s browser within the trust relationship between their browser and the server.
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 · moderate confidenceThis is a reflected cross-site scripting (XSS) vulnerability in the web management interface of Moxa G3100V2 Series (prior to v2.8) and OnCell G3111/G3151/G3211/G3251 Series (prior to v1.7). Attackers can inject malicious script code through unsanitized user input that gets reflected back in HTTP responses, allowing execution in authenticated users' browsers.
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< 2.8< 1.7< 1.7< 1.7< 1.7CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Identify the Moxa device modelAccess the device console or web interface and locate the model identifier (G3100V2, G3111, G3151, G3211, or G3251) in the system information or device status pageAffected if The device model is one of G3100V2, G3111, G3151, G3211, or G3251 series
-
Check the firmware versionIn the device web management interface, navigate to System Settings or Device Information to view the installed firmware version. Alternatively, access the device via console or SNMP to retrieve firmware versionAffected if Firmware version is below 2.8 for G3100V2 or below 1.7 for OnCell G3111/G3151/G3211/G3251 series
-
Verify the web management interface is enabledCheck the device configuration to confirm the HTTP/HTTPS web management interface is currently active. This is typically found under Network Settings or Service Configuration in the web interfaceAffected if The web management interface is enabled and accessible over HTTP or HTTPS
-
Test for reflected XSS vulnerability (optional)If authorized and in a controlled test environment, log into the web interface and observe whether user-supplied input in URL parameters or form fields is reflected back in the response without proper sanitizationAffected if User input is reflected unsanitized in HTTP responses, indicating the XSS vulnerability is present
You are affected if your device is a G3100V2 (firmware < 2.8) or OnCell G3111/G3151/G3211/G3251 (firmware < 1.7) and the web management interface is enabled.
Generated from the published advisory. Verify against your own configuration.
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 data1.72.8
Upgrade Moxa G3100V2 devices to Version 2.8 or later and OnCell G3111/G3151/G3211/G3251 devices to Version 1.7 or later to obtain the patched firmware.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5819 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2016-5819 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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