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

> Cross-site scripting in Reservo Image Hosting allows attackers to steal user and admin sessions via malicious URLs, leading to account takeover.

- **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:** 24 Jan 2018
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-8h5p-57f6-h2jc

## What is CVE-2018-5705?

CVE-2018-5705 is a medium-severity cross-site scripting vulnerability in n/a, published on 24 Jan 2018. 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

Reservo Image Hosting 1.6 is vulnerable to XSS attacks. The affected function is its search engine (the t parameter to the /search URI). Since there is an user/admin login interface, it's possible for attackers to steal sessions of users and thus admin(s). By sending users an infected URL, code will be executed.

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

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

It affects 1 product.


Products: Reservo Image Hosting.

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

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

## Is CVE-2018-5705 being exploited?

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

Public exploit code:

- Reservo Image Hosting Script 1.5 - Cross-Site Scripting (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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