dbcve.org
PiwigoApplication

CVE-2026-27634

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-03
Fix available
A fix is available. Upgrade to 16.3.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click Patch available

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
Piwigo is an open source photo gallery application for the web. Prior to version 16.3.0, the four date filter parameters (f_min_date_available, f_max_date_available, f_min_date_created, f_max_date_created) in ws_std_image_sql_filter() are concatenated directly into SQL without any escaping or type validation. This could result in an unauthenticated attacker reading the full database, including user password hashes. This issue has been patched in version 16.3.0.

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

Piwigo versions prior to 16.3.0 contain a SQL injection vulnerability in the ws_std_image_sql_filter() function. Four date filter parameters (f_min_date_available, f_max_date_available, f_min_date_created, f_max_date_created) are directly concatenated into SQL queries without escaping or type validation, allowing unauthenticated attackers to execute arbitrary SQL and exfiltrate sensitive data including user password hashes.

MitigationUpgrade to Piwigo version 16.3.0 or later, which implements proper SQL parameterization for the affected date filter parameters.

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:< 16.3.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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Determine the installed Piwigo version
    Access the Piwigo administration panel and navigate to Tools > Version, or check the version.php file in the Piwigo root directory if you have file system access
    Affected if The installed version is below 16.3.0
  2. Verify the web services API is accessible
    Check if the ws_std_image_sql_filter() function endpoint is reachable by attempting to access the web services URL (typically /ws.php or /api.php) with a request to the image filtering functionality
    Affected if The Piwigo web services API endpoint is exposed and accessible without authentication
  3. Confirm the vulnerable date filter parameters are accepted
    Send a test request to the Piwigo web services endpoint including one of the four affected parameters (f_min_date_available, f_max_date_available, f_min_date_created, f_max_date_created) with a test value and observe if the application processes the parameter without rejecting or sanitizing the input
    Affected if The application accepts and processes the date filter parameters directly into SQL queries without type validation or escaping

A Piwigo installation is affected if it is running any version before 16.3.0 and has its web services API with image filtering functionality accessible to unauthenticated users.

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
Upgrade available Upgrade to 16.3.0 or later
Fixed in 16.3.0
Vendor patch github.com →
Interim mitigation

Upgrade to Piwigo version 16.3.0 or later, which implements proper SQL parameterization for the affected date filter parameters.

Recommended fix High confidence

Piwigo 16.3.0

  1. 1. Back up your Piwigo database and all application files before proceeding with any changes
  2. 2. Download Piwigo version 16.3.0 from the official Piwigo website (piwigo.org) or GitHub repository
  3. 3. Extract the downloaded archive containing the new version
  4. 4. Replace the existing Piwigo installation files with the files from version 16.3.0, or use the built-in upgrade functionality if available
  5. 5. Verify that the upgrade completed successfully by checking the version number in the Piwigo admin panel
  6. 6. Confirm that the gallery functionality and all plugins/themes work correctly after the upgrade
  7. 7. If the upgrade is successful, the SQL injection vulnerability in ws_std_image_sql_filter() will be patched as the date filter parameters are now properly escaped and validated
Caveat Review the Piwigo 16.3.0 release notes for any breaking changes, deprecations, or required database migrations before upgrading

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

Fix this in Piwigo Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-27634 — 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-2026-27634 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