# CVE-2015-6402: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML into the management interface of Cisco EPC3928 devices, potentially compromising user sessions.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 14 Dec 2015
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-79cv-2938-whjg

## What is CVE-2015-6402?

CVE-2015-6402 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 Dec 2015. It can be exploited over the network, and only if a user opens a file or follows a link.

### Official description

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.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

## Which versions are affected by CVE-2015-6402?

It affects 1 product.


Products: Cisco Epc3928 Docsis 3.0 8x4 Wireless Residential Gateway With Embedded Digital Voice Adapter.

## How do I fix CVE-2015-6402?

No fix has been published for CVE-2015-6402 yet. Limit exposure of the affected software until one is available.

## Is CVE-2015-6402 being exploited?

There is no known exploitation of CVE-2015-6402 in the wild and no public exploit code.

Public exploit code:

- Cisco EPC 3928 - Multiple Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2015-6401](https://insights.sbomify.com/CVE-2015-6401/): Auth bypass in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-6402 and fix it if it is affected.

What it is: CVE-2015-6402 is a medium-severity cross-site scripting vulnerability in n/a, published on 14 Dec 2015. It can be exploited over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2015-6402 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2015-6402/ (Markdown: https://insights.sbomify.com/CVE-2015-6402/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2015-6402
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2015-6402
- OSV: https://osv.dev/vulnerability/CVE-2015-6402

---
From sbomify Insights: https://insights.sbomify.com/CVE-2015-6402/
Summaries are generated and may contain mistakes; the official description above is the record.