CVE-2024-51144: Cross-Site Request Forgery (CSRF)
Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 14:05 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 5 Mar 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
AI-suggested
- Immediately restrict external access to Ampache instances by implementing network-level controls such as firewalls or VPNs to limit usage to trusted internal networks.
- Employ web application firewalls (WAFs) with custom rules to detect and block suspicious CSRF attack patterns targeting the vulnerable endpoints.
- Advise users to avoid clicking on untrusted links or visiting suspicious websites while logged into Ampache to reduce the risk of CSRF exploitation.
- Monitor web server logs for unusual POST requests to the affected endpoints that could indicate attempted exploitation.
- If possible, temporarily disable or restrict functionality of the vulnerable endpoints until an official patch is released.
- Engage with the Ampache community or maintainers to track patch releases and apply updates promptly once available.
- Implement additional CSRF protections such as synchronizer tokens or same-site cookies if custom modifications to the Ampache codebase are feasible.
- Conduct user awareness training focused on phishing and social engineering risks that could facilitate CSRF attacks.
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.