What is the CVSS score of CVE-2020-16210?

CVE-2020-16210 has a CVSS 3.1 base score of 9.0 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:H. EPSS exploitation probability: 3.2%.

Is there a public PoC exploit available for CVE-2020-16210?

Yes, a public proof-of-concept exploit is available for CVE-2020-16210. Prioritise patching immediately. EPSS: 3.2%.

N Tron 702 W Firmware CVE-2020-16210

CRITICAL

Cross-site Scripting (XSS) (CWE-79)

2020-09-01 ics-cert@hq.dhs.gov

XSS RCE N Tron 702 W Firmware N Tron 702M12 W Firmware

9.0

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.0 CRITICAL

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Sep 01, 2020 - 21:15 nvd

CRITICAL 9.0

DescriptionNVD

AnalysisAI

The affected product is vulnerable to reflected cross-site scripting, which may allow an attacker to remotely execute arbitrary code and perform actions in the context of an attacked user on the. Rated critical severity (CVSS 9.0), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as Cross-Site Scripting (XSS) (CWE-79), which allows attackers to inject malicious scripts into web pages viewed by other users. The affected product is vulnerable to reflected cross-site scripting, which may allow an attacker to remotely execute arbitrary code and perform actions in the context of an attacked user on the N-Tron 702-W / 702M12-W (all versions). Affected products include: Redlion N-Tron 702-W Firmware, Redlion N-Tron 702M12-W Firmware.

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Sanitize all user input, use Content-Security-Policy headers, encode output contextually (HTML, JS, URL). Use frameworks with built-in XSS protection.