What is the CVSS score of CVE-2017-8839?

CVE-2017-8839 has a CVSS 3.0 base score of 6.1 (Medium). CVSS vector: CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N. EPSS exploitation probability: 2.0%.

Is there a public PoC exploit available for CVE-2017-8839?

Yes, a public proof-of-concept exploit is available for CVE-2017-8839. Prioritise patching immediately. EPSS: 2.0%.

B305Hw2 Firmware CVE-2017-8839

MEDIUM

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

2017-06-05 cve@mitre.org

XSS B305Hw2 Firmware 380Hw6 Firmware 580Hw2 Firmware 710Hw3 Firmware 1350Hw2 Firmware 2500 Firmware

6.1

CVSS 3.0 · NVD

Severity by source

NVD PRIMARY

6.1 MEDIUM

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

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

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

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Changed

Confidentiality

Low

Integrity

Low

Availability

None

Lifecycle Timeline

CVE Published

Jun 05, 2017 - 14:29 cve.org

MEDIUM 6.1

DescriptionCVE.org

AnalysisAI

XSS via orig_url exists on Peplink Balance 305, 380, 580, 710, 1350, and 2500 devices with firmware before fw-b305hw2_380hw6_580hw2_710hw3_1350hw2_2500-7.0.1-build2093. Rated medium severity (CVSS 6.1), this vulnerability is remotely exploitable, no authentication required, 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. XSS via orig_url exists on Peplink Balance 305, 380, 580, 710, 1350, and 2500 devices with firmware before fw-b305hw2_380hw6_580hw2_710hw3_1350hw2_2500-7.0.1-build2093. The affected script is guest/preview.cgi. Affected products include: Peplink B305Hw2 Firmware, Peplink 380Hw6 Firmware, Peplink 580Hw2 Firmware, Peplink 710Hw3 Firmware, Peplink 1350Hw2 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.