Skip to main content
No exploitation reportedFix available

CVE-2016-5804

No exploitation reported by the sources we read.

  • Published2016-07-15
  • Fixed in2.5
  • WeaknessCWE-326

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

Moxa MGate MB3180 before 1.8, MGate MB3280 before 2.7, MGate MB3480 before 2.6, MGate MB3170 before 2.5, and MGate MB3270 before 2.7 use weak encryption, which allows remote attackers to bypass authentication via a brute-force series of guesses for a parameter value.

Timeline

dates in UTC
  1. 2016-07-1516:59CVE publishedNVD

Observed activity

isMalicious corpus · updated 2026-10-23 18:48 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2016-5804?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2016-5804?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Moxa mgate mb3170 firmwareversion to verify
BranchAffectedFixed in
2.5< 2.52.5
Moxa mgate mb3180 firmwareversion to verify
BranchAffectedFixed in
1.8< 1.81.8
Moxa mgate mb3270 firmwareversion to verify
BranchAffectedFixed in
2.7< 2.72.7

2 more products in the sources.

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Distribution builds and vendor advisories

Packages from OSV.dev and products from the vendors' CSAF advisories.

version not verifiedVersions not verified: read as OSV.dev and the vendors publish them, not checked against each vendor's release list.

Vendor advisories

  • ICSA-16-196-02 CISA5 known affected

    Moxa MGate Authentication Bypass Vulnerability

    Moxa MGate MB3180: <=v1.8 · Moxa MGate MB3280: <=v2.7 · Moxa MGate MB3480: <=v2.6 · +2 more

Full record on NVD

Fix

  1. Update Moxa mgate mb3170 firmware to 2.5
  2. Mitigation from the vendor CISA ICSA-16-196-02 · 5 productsMoxa has released new versions of firmware, which has enhanced the security of the MB3x70 and MB3x80 families. This new firmware can be located on its web site at the following locations: MB3180, v1.8, MB3280, v2.7, and MB3480, v2.6 (http://www.moxa.com/support/sarch_result.aspx?type=soft&prod_id=7…
  3. Mitigation from the vendor CISA ICSA-16-196-02 · 5 productsMB3170, v2.5 and MB3270, v2.7 (http://www.moxa.com/support/sarch_result.aspx?type=soft&prod_id=74&type_id=4)

Detection

Nuclei template
none so far
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
none listed
PoC-in-GitHub

Sources

  • NVDCVSS 3.19.8read 2026-10-23
  • NVDCVSS 2.05read 2026-10-23
  • NVDweakness (CWE)CWE-326read 2026-10-23
  • FIRST EPSSEPSS score1.1 %2026-10-22

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2016-07-15
Last Modified
2026-06-17
NVD status
Modified

Frequently asked questions

What is CVE-2016-5804?

Moxa MGate MB3180 before 1.8, MGate MB3280 before 2.7, MGate MB3480 before 2.6, MGate MB3170 before 2.5, and MGate MB3270 before 2.7 use weak encryption, which allows remote attackers to bypass authentication via a brute-force series of guesses for a parameter value.

Is CVE-2016-5804 actively exploited?

Active exploitation of CVE-2016-5804 has not been confirmed. Its EPSS score was 1.1% on 2026-10-22, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2016-5804?

CVE-2016-5804 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Hear about the next vulnerability in your software

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

No credit card required · No monthly cap on website lookups · 250 API requests/month