# CVE-2024-54819: Server-side request forgery in n/a

> An attacker can exploit improper input validation in I, Librarian to perform Server-Side Request Forgery, potentially accessing internal resources.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Jan 2025
- **Updated:** 17 Mar 2026
- **Also known as:** GHSA-9w8w-fgjg-w972

## What is CVE-2024-54819?

CVE-2024-54819 is a critical server-side request forgery vulnerability in n/a, published on 7 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

I, Librarian before and including 5.11.1 is vulnerable to Server-Side Request Forgery (SSRF) due to improper input validation in classes/security/validation.php

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2024-54819?


## How do I fix CVE-2024-54819?

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

## Is CVE-2024-54819 being exploited?

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

Public exploit code:

- CVE-2024-54819 (github_poc): https://github.com/partywavesec/CVE-2024-54819

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-54819 and fix it if it is affected.

What it is: CVE-2024-54819 is a critical server-side request forgery vulnerability in n/a, published on 7 Jan 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-54819 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-2024-54819/ (Markdown: https://insights.sbomify.com/CVE-2024-54819/index.md)
```

## Sources

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

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