# CVE-2025-61488: Server-side request forgery in n/a

> Remote attackers can execute arbitrary code via the scrap_image.php component in Senayan Library Management System.

- **Severity:** High 7.6 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 20 Oct 2025
- **Updated:** 20 Oct 2025
- **Also known as:** GHSA-cch2-42p7-w83v

## What is CVE-2025-61488?

CVE-2025-61488 is a high-severity server-side request forgery vulnerability in n/a, published on 20 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

An issue in Senayan Library Management System (SLiMS) 9 Bulian v.9.6.1 allows a remote attacker to execute arbitrary code via the scrap_image.php component and the imageURL parameter

Weakness: CWE-94 (Improper Control of Generation of Code), CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2025-61488?


## How do I fix CVE-2025-61488?

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

## Is CVE-2025-61488 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-61488 and fix it if it is affected.

What it is: CVE-2025-61488 is a high-severity server-side request forgery vulnerability in n/a, published on 20 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-61488 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-2025-61488/ (Markdown: https://insights.sbomify.com/CVE-2025-61488/index.md)
```

## Sources

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

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