# CVE-2019-7687: Cross-site scripting in n/a

> Reflected XSS in JioFi 4 hotspot web interface allows attackers to execute scripts in user browsers via the Page parameter.

- **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:** 7 May 2019
- **Updated:** 4 Aug 2024
- **Also known as:** GHSA-2cxx-gfmw-p9v8

## What is CVE-2019-7687?

CVE-2019-7687 is a medium-severity cross-site scripting vulnerability in n/a, published on 7 May 2019. 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

cgi-bin/qcmap_web_cgi on JioFi 4 jmr1140 Amtel_JMR1140_R12.07 devices has POST based reflected XSS via the Page parameter. No sanitization is performed for user input data.

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

## Which versions are affected by CVE-2019-7687?

It affects 1 product.


Products: Jio Jmr1140 Firmware.

## How do I fix CVE-2019-7687?

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

## Is CVE-2019-7687 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2019-7745](https://insights.sbomify.com/CVE-2019-7745/): Information disclosure in n/a (critical 9.8)
- [CVE-2019-7746](https://insights.sbomify.com/CVE-2019-7746/): Cross-site request forgery in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2019-7687 and fix it if it is affected.

What it is: CVE-2019-7687 is a medium-severity cross-site scripting vulnerability in n/a, published on 7 May 2019. 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-2019-7687 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-2019-7687/ (Markdown: https://insights.sbomify.com/CVE-2019-7687/index.md)
```

## Sources

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

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