# CVE-2026-42323: Piwigo: SQL Injection in Batch Manager

> An authenticated administrator can exploit SQL injection in the Batch Manager to disclose, modify, or disrupt database data.

- **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:** 28 Sep 2026
- **Also known as:** GHSA-7r67-9xhq-7p2c

## What is CVE-2026-42323?

CVE-2026-42323 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/batch_manager.php accepts administrator-controlled dimension width, height, and ratio values and filesize values from the Batch Manager filter URL without numeric validation. The URL filter parser stores those values in the bulk_manager_filter session state, and later query construction concatenates them into SQL predicates, unlike the validated POST filter path. An authenticated administrator can use crafted filter values to execute time-based or other SQL expressions and potentially 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-42323?


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

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

## Is CVE-2026-42323 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-42323 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-42323 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-42323/ (Markdown: https://insights.sbomify.com/CVE-2026-42323/index.md)
```

## Sources

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

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