# CVE-2018-25101: l2c2technologies Koha opac-MARCdetail.pl cross site scripting

> Remote attackers can execute arbitrary scripts in Koha via XSS in opac-MARCdetail.pl, potentially compromising user sessions.

- **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:** 22 Apr 2024
- **Updated:** 5 Aug 2024
- **Also known as:** GHSA-9wh7-fr57-h2j7

## What is CVE-2018-25101?

CVE-2018-25101 is a low-severity cross-site scripting vulnerability in l2c2technologies Koha, published on 22 Apr 2024. 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, which was classified as problematic, has been found in l2c2technologies Koha up to 20180108. This issue affects some unknown processing of the file /cgi-bin/koha/opac-MARCdetail.pl. The manipulation of the argument biblionumber with the input 2"><TEST> leads to cross site scripting. The attack may be initiated remotely. The identifier of the patch is 950fc8e101886821879066b33e389a47fb0a9782. It is recommended to upgrade the affected component. The identifier VDB-261677 was assigned to this vulnerability.

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

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


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

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

## Is CVE-2018-25101 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2018-25101 is a low-severity cross-site scripting vulnerability in l2c2technologies Koha, published on 22 Apr 2024. 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-25101 in the wild and no public exploit code.

Affected product: l2c2technologies Koha. 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-25101/ (Markdown: https://insights.sbomify.com/CVE-2018-25101/index.md)
```

## Sources

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

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