# CVE-2018-15181: Cross-site scripting in n/a

> Attackers can cause a denial of service on JioFi 4G Hotspot devices by injecting XSS payloads into SSID and Security Key fields.

- **Severity:** Medium 6.5 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Aug 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-86p3-4785-rm9c

## What is CVE-2018-15181?

CVE-2018-15181 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

JioFi 4G Hotspot M2S devices allow attackers to cause a denial of service (secure configuration outage) via an XSS payload in the SSID name and Security Key fields.

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

## Which versions are affected by CVE-2018-15181?

It affects 1 product.


Products: Jio 4g Hotspot M2s Firmware.

## How do I fix CVE-2018-15181?

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

## Is CVE-2018-15181 being exploited?

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

Public exploit code:

- JioFi 4G M2S 1.0.2 - Denial of Service (PoC) (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2018-15181 and fix it if it is affected.

What it is: CVE-2018-15181 is a medium-severity cross-site scripting vulnerability in n/a, published on 9 Aug 2018. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2018-15181 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-2018-15181/ (Markdown: https://insights.sbomify.com/CVE-2018-15181/index.md)
```

## Sources

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

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