# CVE-2024-51144: Cross-site request forgery in n/a

> Attackers can force authenticated users to perform unintended actions like adding messages or deleting items in Ampache.

- **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:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 5 Mar 2025
- **Updated:** 30 Sep 2025
- **Also known as:** GHSA-j3gx-p9r2-3cwr, UBUNTU-CVE-2024-51144

## What is CVE-2024-51144?

CVE-2024-51144 is a high-severity vulnerability in n/a, published on 5 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross Site Request Forgery (CSRF) vulnerability exists in the 'pvmsg.php?action=add_message', pvmsg.php?action=confirm_delete , and ajax.server.php?page=user&action=flip_follow endpoints in Ampache <= 6.6.0.

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

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


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

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

## Is CVE-2024-51144 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-51144 is a high-severity vulnerability in n/a, published on 5 Mar 2025. An attacker can exploit it over the internet without logging in, 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-2024-51144 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-51144/ (Markdown: https://insights.sbomify.com/CVE-2024-51144/index.md)
```

## Sources

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

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