Skip to content
Fencer Intel
high 8.8

CVE-2020-16208 json

The affected product is vulnerable to cross-site request forgery, which may allow an attacker to modify different configurations of a devic…

published 6y ago modified 4mo ago also EUVD-2020-8174

cvss
8.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
1.2%
EPSS 1.2% chance of exploitation in 30 days, percentile 69%
public exploits
0
none known

Summary

The affected product is vulnerable to cross-site request forgery, which may allow an attacker to modify different configurations of a device by luring an authenticated user to click on a crafted link on the N-Tron 702-W / 702M12-W (all versions).

Is CVE-2020-16208 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

cisa ICSA-20-240-01 updated cvss 8.8

Red Lion N-Tron 702-W, 702M12-W

  • Red Lion, AutomationDirect N-Tron 702-W Red Lion, AutomationDirect N-Tron 702M12-W
    affected: mitigation “Red Lion's 702-W Series was discontinued in 2018 and cannot be updated. Red Lion recommends these products be used locally within a secure network.”

From CISA ICS and IT advisories (CSAF, https://github.com/cisagov/CSAF), a U.S. Government work; changed: reduced to products, statuses and remediations. CISA notification · csaf

Exploit prediction

1.24% chance of exploitation in the next 30 days, higher than 69% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 8.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
NVD 2.0 9.3 AV:N/AC:M/Au:N/C:C/I:C/A:C

Affected products

  • n/a N-Tron 702-W / 702M12-W

Classification

Weakness
  • CWE-352 Cross-Site Request Forgery

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.