# CVE-2026-107084: Cross-site request forgery in n/a

> An attacker can trick an authenticated admin into deleting loan history records via a crafted link, causing data loss in Slims.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 19 Oct 2026
- **Updated:** 26 Oct 2026
- **Also known as:** GHSA-2h92-7h5x-98h5

## What is CVE-2026-107084?

CVE-2026-107084 is a high-severity vulnerability in n/a, published on 19 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Slims (Senayan Library Management Systems) 9 Bulian 9.8.0 allows cross-site request forgery (CSRF) against admin/modules/circulation/loan_history_maintenance.php because the action=run GET parameter performs privileged, destructive operations with no CSRF token or POST confirmation, leading to data loss of loan history records.

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

## Which versions are affected by CVE-2026-107084?


## How do I fix CVE-2026-107084?

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

## Is CVE-2026-107084 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107084 exists.

Public exploit code:

- CSRF in SLiMS 9.8.0 loan history maintenance allowing unauthorized data loss (TRUNCATE). CVE-2026-107084. (github_poc): https://github.com/Primandito/CVE-2026-107084

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107084 and fix it if it is affected.

What it is: CVE-2026-107084 is a high-severity vulnerability in n/a, published on 19 Oct 2026. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107084 exists.

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-2026-107084/ (Markdown: https://insights.sbomify.com/CVE-2026-107084/index.md)
```

## Sources

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

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