Skip to main content
CVE-2024-51144VulnerabilityPublished Updated

CVE-2024-51144: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
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:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Mar 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq 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 2026-10-25.

What to do

AI-suggested

1. Immediately restrict external access to Ampache instances by implementing network-level controls such as firewalls or VPNs to limit usage to trusted internal networks. 2. Employ web application firewalls (WAFs) with custom rules to detect and block suspicious CSRF attack patterns targeting the vulnerable endpoints. 3. Advise users to avoid clicking on untrusted links or visiting suspicious websites while logged into Ampache to reduce the risk of CSRF exploitation. 4. Monitor web server logs for unusual POST requests to the affected endpoints that could indicate attempted exploitation. 5. If possible, temporarily disable or restrict functionality of the vulnerable endpoints until an official patch is released. 6. Engage with the Ampache community or maintainers to track patch releases and apply updates promptly once available. 7. Implement additional CSRF protections such as synchronizer tokens or same-site cookies if custom modifications to the Ampache codebase are feasible. 8. 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.

References

Community reviews

Loading reviews…