What is the CVSS score of CVE-2015-6402?

CVE-2015-6402 has a CVSS 2.0 base score of 4.3 (Medium). CVSS vector: AV:N/AC:M/Au:N/C:N/I:P/A:N. EPSS exploitation probability: 34.3%.

Is there a public PoC exploit available for CVE-2015-6402?

Yes, a public proof-of-concept exploit is available for CVE-2015-6402. Prioritise patching immediately. EPSS: 34.3%.

Epc3928 Docsis 3 0 8X4 Wireless Residential Gateway With Embedded Digital Voice Adapter CVE-2015-6402

MEDIUM

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

2015-12-14 psirt@cisco.com

XSS Cisco Epc3928 Docsis 3 0 8X4 Wireless Residential Gateway With Embedded Digital Voice Adapter

4.3

CVSS 2.0 · NVD

Severity by source

NVD PRIMARY

4.3 MEDIUM

AV:N/AC:M/Au:N/C:N/I:P/A:N

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

AV:N/AC:M/Au:N/C:N/I:P/A:N

Attack Vector

Network

Attack Complexity

Confidentiality

None

Integrity

Availability

None

Lifecycle Timeline

CVE Published

Dec 14, 2015 - 03:59 cve.org

MEDIUM 4.3

DescriptionCVE.org

AnalysisAI

Cross-site scripting (XSS) vulnerability in the management interface on Cisco EPC3928 devices with EDVA 5.5.10, 5.5.11, and 5.7.1 allows remote attackers to inject arbitrary web script or HTML via an. Rated medium severity (CVSS 4.3), this vulnerability is remotely exploitable. Public exploit code available and EPSS exploitation probability 34.3%.

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. Cross-site scripting (XSS) vulnerability in the management interface on Cisco EPC3928 devices with EDVA 5.5.10, 5.5.11, and 5.7.1 allows remote attackers to inject arbitrary web script or HTML via an unspecified value, aka Bug ID CSCux24935. Affected products include: Cisco Epc3928 Docsis 3.0 8X4 Wireless Residential Gateway With Embedded Digital Voice Adapter.

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.