# CVE-2018-25064: OSM Lab show-me-the-way site.js cross site scripting

> A cross-site scripting vulnerability in OSM Lab show-me-the-way allows remote attackers to inject malicious scripts via the site.js file.

- **Severity:** Low 3.5 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Jan 2023
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-jcgv-r252-27j3

## What is CVE-2018-25064?

CVE-2018-25064 is a low-severity cross-site scripting vulnerability in OSM Lab show-me-the-way, published on 5 Jan 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A vulnerability was found in OSM Lab show-me-the-way. It has been rated as problematic. This issue affects some unknown processing of the file js/site.js. The manipulation leads to cross site scripting. The attack may be initiated remotely. The patch is named 4bed3b34dcc01fe6661f39c0e5d2285b340f7cac. It is recommended to apply a patch to fix this issue. The associated identifier of this vulnerability is VDB-217439.

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

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

It affects 1 product.


Products: Show-Me-the-Way Project Show-Me-the-Way.

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

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

## Is CVE-2018-25064 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25064 is a low-severity cross-site scripting vulnerability in OSM Lab show-me-the-way, published on 5 Jan 2023. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2018-25064 in the wild and no public exploit code.

Affected product: OSM Lab show-me-the-way. 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-25064/ (Markdown: https://insights.sbomify.com/CVE-2018-25064/index.md)
```

## Sources

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

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