What is the CVSS score of CVE-2023-4203?

CVE-2023-4203 has a CVSS 3.1 base score of 5.4 (Medium). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N. EPSS exploitation probability: 0.9%.

Is there a public PoC exploit available for CVE-2023-4203?

Yes, a public proof-of-concept exploit is available for CVE-2023-4203. Prioritise patching immediately. EPSS: 0.9%.

Eki 1524 Firmware CVE-2023-4203

MEDIUM

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

2023-08-08 office@cyberdanube.com

XSS Eki 1524 Firmware Eki 1522 Firmware Eki 1521 Firmware

5.4

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

5.4 MEDIUM

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

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:L/I:L/A:N

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

CVE Published

Aug 08, 2023 - 11:15 nvd

MEDIUM 5.4

DescriptionNVD

AnalysisAI

Advantech EKI-1524, EKI-1522, EKI-1521 devices through 1.21 are affected by a Stored Cross-Site Scripting vulnerability, which can be triggered by authenticated users in the ping tool of the. Rated medium severity (CVSS 5.4), 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. Advantech EKI-1524, EKI-1522, EKI-1521 devices through 1.21 are affected by a Stored Cross-Site Scripting vulnerability, which can be triggered by authenticated users in the ping tool of the web-interface. Affected products include: Advantech Eki-1524 Firmware, Advantech Eki-1522 Firmware, Advantech Eki-1521 Firmware. Version information: through 1.21.

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.