# CVE-2026-93484: SQL injection in Znuny

> Attackers can inject SQL via the ContentSearch parameter in Znuny to steal, modify, or disrupt ticket data.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:L/SI:L/SA:N/AU:Y/R:U/RE:M/U:Amber`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** DEBIAN-CVE-2026-93484, GHSA-mxcg-m44c-38cw, UBUNTU-CVE-2026-93484

## What is CVE-2026-93484?

CVE-2026-93484 is a high-severity SQL injection vulnerability in Znuny, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Znuny through 7.3.6 constructs a ticket-search database query by directly concatenating user-supplied input into the SQL statement. This lack of proper sanitization or the use of parameterized queries allows an attacker to inject arbitrary SQL commands, leading to data theft, modification, or denial of service. Specifically this is in Kernel::System::Ticket::TicketSearch and Kernel::System::Ticket::ArticleSearchIndex::DB via the ContentSearch parameter. The parameter is expected to be either "AND" or "OR", but its value was concatenated directly into the generated SQL query without validation.

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

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


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

Apply the vendor's patch.

## Is CVE-2026-93484 being exploited?

There is no known exploitation of CVE-2026-93484 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-93484 is a high-severity SQL injection vulnerability in Znuny, published on 15 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-93484 in the wild and no public exploit code.

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

## Sources

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

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