Skip to main content
VulnerabilityPublished

CVE-2024-48311: Piwigo · Cross-Site Request Forgery (CSRF)

Affects PiwigoSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 28% 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 31 Oct 2024

  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 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubwhiteshark2k/Piwigopkg:github/whiteshark2k/PiwigoOther threatsAffected
  • =14.5.0
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-48311, organizations should immediately implement the following measures: 1) Disable or restrict access to the Edit album functionality until a vendor patch is available. 2) Implement anti-CSRF tokens in all state-changing requests to ensure that requests originate from legitimate users. 3) Enforce strict SameSite cookie attributes to reduce CSRF attack vectors. 4) Educate users about the risks of clicking on suspicious links and the importance of logging out from Piwigo sessions when not in use. 5) Monitor web server and application logs for unusual or unauthorized album edit requests. 6) If possible, deploy Web Application Firewalls (WAFs) with rules to detect and block CSRF attack patterns targeting Piwigo endpoints. 7) Stay updated with vendor advisories and apply official patches promptly once released. These steps go beyond generic advice by focusing on immediate functional restrictions, user awareness, and layered defenses tailored to the vulnerability’s nature.

Description

Piwigo v14.5.0 was discovered to contain a Cross-Site Request Forgery (CSRF) via the Edit album function.

References

Community reviews

Loading reviews…