# CVE-2015-4630: Cross-site request forgery in n/a

> Remote attackers can exploit CSRF flaws in Koha to hijack administrator sessions, create users, or grant superlibrarian privileges.

- **Severity:** High 8.0 (`CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H`)
- **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:** 18 Oct 2018
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-85vr-q6xj-xf78

## What is CVE-2015-4630?

CVE-2015-4630 is a high-severity vulnerability in n/a, published on 18 Oct 2018. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site request forgery (CSRF) vulnerabilities in Koha 3.14.x before 3.14.16, 3.16.x before 3.16.12, 3.18.x before 3.18.08, and 3.20.x before 3.20.1 allow remote attackers to (1) hijack the authentication of administrators for requests that create a user via a request to members/memberentry.pl or (2) give a user superlibrarian permission via a request to members/member-flags.pl or (3) hijack the authentication of arbitrary users for requests that conduct cross-site scripting (XSS) attacks via the addshelf parameter to opac-shelves.pl.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2015-4630?

It affects 1 product.


Products: Koha Koha.

## How do I fix CVE-2015-4630?

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

## Is CVE-2015-4630 being exploited?

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

Public exploit code:

- Koha 3.20.1 - Multiple Cross-Site Scripting / Cross-Site Request Forgery Vulnerabilities (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2014-1924](https://insights.sbomify.com/CVE-2014-1924/): SQL injection in n/a (critical 9.8)
- [CVE-2014-1925](https://insights.sbomify.com/CVE-2014-1925/): SQL injection in n/a (critical 9.8)
- [CVE-2015-4633](https://insights.sbomify.com/CVE-2015-4633/): SQL injection in n/a (critical 9.8)
- [CVE-2024-28739](https://insights.sbomify.com/CVE-2024-28739/): Command injection in n/a (critical 9.6)
- [CVE-2024-24337](https://insights.sbomify.com/CVE-2024-24337/): Code injection in n/a (high 8.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2015-4630 and fix it if it is affected.

What it is: CVE-2015-4630 is a high-severity vulnerability in n/a, published on 18 Oct 2018. 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-2015-4630 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-2015-4630/ (Markdown: https://insights.sbomify.com/CVE-2015-4630/index.md)
```

## Sources

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

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