# CVE-2017-8839: Cross-site scripting in n/a

> Cross-site scripting vulnerability in Peplink Balance routers allows attackers to inject malicious scripts via the orig_url parameter in the guest preview interface.

- **Severity:** Medium 6.1 (`CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Jun 2017
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-qrf5-g9cq-r2h6

## What is CVE-2017-8839?

CVE-2017-8839 is a medium-severity cross-site scripting vulnerability in n/a, published on 5 Jun 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

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.

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

## Which versions are affected by CVE-2017-8839?

It affects 6 products.


Products: Peplink 1350hw2 Firmware, Peplink 2500 Firmware, Peplink 380hw6 Firmware, Peplink 580hw2 Firmware, Peplink 710hw3 Firmware, Peplink B305hw2 Firmware.

## How do I fix CVE-2017-8839?

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

## Is CVE-2017-8839 being exploited?

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

Public exploit code:

- Peplink Balance Routers 7.0.0-build1904 - SQL Injection / Cross-Site Scripting / Information Disclosure (exploitdb)
- Peplink Balance Routers 7.0.0-build1904 - SQL Injection / Cross-Site Scripting / Information Disclosure (exploitdb)
- Peplink Balance Routers 7.0.0-build1904 - SQL Injection / Cross-Site Scripting / Information Disclosure (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2017-8835](https://insights.sbomify.com/CVE-2017-8835/): SQL injection in n/a (critical 9.8)
- [CVE-2017-8837](https://insights.sbomify.com/CVE-2017-8837/): Hardcoded credentials in n/a (critical 9.8)
- [CVE-2017-8836](https://insights.sbomify.com/CVE-2017-8836/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2017-8841](https://insights.sbomify.com/CVE-2017-8841/): Path traversal in n/a (high 8.1)
- [CVE-2017-8838](https://insights.sbomify.com/CVE-2017-8838/): Cross-site scripting in n/a (medium 6.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2017-8839 and fix it if it is affected.

What it is: CVE-2017-8839 is a medium-severity cross-site scripting vulnerability in n/a, published on 5 Jun 2017. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2017-8839 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-2017-8839/ (Markdown: https://insights.sbomify.com/CVE-2017-8839/index.md)
```

## Sources

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

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