# CVE-2026-3292: jizhiCMS Batch Model.php findAll sql injection

> Remote attackers can exploit SQL injection in jizhiCMS Batch Interface to read or modify database contents.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 27 Feb 2026
- **Updated:** 27 Feb 2026
- **Also known as:** GHSA-rwvh-hmmf-wpqx

## What is CVE-2026-3292?

CVE-2026-3292 is a medium-severity SQL injection vulnerability in jizhiCMS, published on 27 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A security vulnerability has been detected in jizhiCMS up to 2.5.6. Affected is the function findAll in the library frphp/lib/Model.php of the component Batch Interface. The manipulation of the argument data leads to sql injection. The attack is possible to be carried out remotely. The exploit has been disclosed publicly and may be used. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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

It affects 1 product.


Products: Jizhicms Jizhicms.

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

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

## Is CVE-2026-3292 being exploited?

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

## Other vulnerabilities in jizhiCMS

- [CVE-2025-50229](https://insights.sbomify.com/CVE-2025-50229/): SQL injection in n/a (critical 9.8)
- [CVE-2025-25784](https://insights.sbomify.com/CVE-2025-25784/): File upload in n/a (critical 9.8)
- [CVE-2024-32161](https://insights.sbomify.com/CVE-2024-32161/): File upload in n/a (critical 9.8)
- [CVE-2023-51154](https://insights.sbomify.com/CVE-2023-51154/): Path traversal in n/a (critical 9.8)
- [CVE-2021-36484](https://insights.sbomify.com/CVE-2021-36484/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-3292 is a medium-severity SQL injection vulnerability in jizhiCMS, published on 27 Feb 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-3292 exists.

Affected product: jizhiCMS. 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-3292/ (Markdown: https://insights.sbomify.com/CVE-2026-3292/index.md)
```

## Sources

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

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