# CVE-2026-42324: Piwigo: Second-Order SQL Injection

> An authenticated administrator can exploit a second-order SQL injection in Piwigo to read, modify, or disrupt database data via crafted image order expressions.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2026
- **Updated:** 25 Sep 2026
- **Also known as:** GHSA-jhp4-7f82-8f6q

## What is CVE-2026-42324?

CVE-2026-42324 is a high-severity SQL injection vulnerability in Piwigo, published on 25 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Piwigo is a full featured open source photo gallery application for the web. Prior to 16.4.0, admin/element_set_ranks.php stores administrator-controlled image_order[] values without enforcing the existing sort-field whitelist. The stored album image_order expression is later concatenated into ORDER BY clauses by admin/batch_manager_global.php, admin/batch_manager_unit.php, include/section_init.inc.php, and include/ws_functions/pwg.categories.php. When at least one album contains at least one photo, an authenticated administrator can store a crafted expression and trigger it in a later album or Batch Manager query to disclose, modify, or disrupt database data. This issue is fixed in version 16.4.0.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2026-42324?


## How do I fix CVE-2026-42324?

No fix has been published for CVE-2026-42324 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-42324 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42324 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-42324 and fix it if it is affected.

What it is: CVE-2026-42324 is a high-severity SQL injection vulnerability in Piwigo, published on 25 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-42324 exists.

Affected product: Piwigo. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-42324/ (Markdown: https://insights.sbomify.com/CVE-2026-42324/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-42324
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-42324
- OSV: https://osv.dev/vulnerability/CVE-2026-42324

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-42324/
Summaries are generated and may contain mistakes; the official description above is the record.