dbcve.org
PiwigoApplication

CVE-2024-26450

MEDIUM · 5.4 CVSS v3.1 Published 2024-02-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
61/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
An issue exists within Piwigo before v.14.2.0 allowing a malicious user to take over the application. This exploit involves chaining a Cross Site Request Forgery vulnerability to issue a Stored Cross Site Scripting payload stored within an Admin user's dashboard, executing remote JavaScript. This can be used to upload a new PHP file under an administrator and directly call that file from the victim's instance to connect back to a malicious listener.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A chained attack in Piwigo before v14.2.0 allows malicious users to combine a CSRF vulnerability with stored XSS. The attacker tricks an admin user into triggering a CSRF request that injects a persistent XSS payload into the admin dashboard. When the admin views the compromised content, the XSS executes JavaScript that uploads a malicious PHP file under administrator privileges, enabling remote code execution via a callback to a malicious listener.

MitigationUpgrade to Piwigo v14.2.0 or later, which implements CSRF token validation and proper input sanitization to prevent both the CSRF exploitation and XSS injection vectors.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
PiwigoApplication
Affected:> 14.2.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Piwigo version
    Check the version.php file in the Piwigo include directory, or view the footer of any Piwigo admin page which typically displays the version number
    Affected if The installed version is lower than 14.2.0 (e.g., 14.1.0, 14.0.0, or earlier releases)
  2. Verify CSRF protection status
    Inspect the source code of forms that perform privileged actions (such as category creation, user management, or plugin installation). Look for a CSRF token validation call using pwg_token() or similar token check functions
    Affected if Forms lack token validation logic and the Piwigo version is below 14.2.0
  3. Check for XSS sanitization in admin input fields
    Examine the PHP code handling admin dashboard inputs (e.g., category description, localfiles editor, or plugin/theme configuration). Look for output encoding or sanitization functions like htmlspecialchars() before rendering user-supplied data
    Affected if User inputs are rendered in the admin interface without proper encoding and the version is below 14.2.0

You are affected if your Piwigo installation version is below 14.2.0 and lacks CSRF token validation on admin forms combined with missing input sanitization on admin dashboard content fields.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Piwigo v14.2.0 or later, which implements CSRF token validation and proper input sanitization to prevent both the CSRF exploitation and XSS injection vectors.

Recommended fix High confidence

Piwigo v14.2.0 or later

  1. Backup the Piwigo database and files before upgrading
  2. Download Piwigo v14.2.0 or later from the official source (piwigo.org)
  3. Follow the standard Piwigo upgrade procedure: upload the new files, run the upgrade script if required, or use the admin dashboard upgrade function
  4. Clear any cache if configured
  5. Verify the upgrade was successful by logging in and checking the version
Caveat Review release notes for any breaking changes between your current version and v14.2.0; test in a staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Piwigo Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-26450 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-26450 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data