# CVE-2025-59816: Authenticated Union based SQL-injection in the search input field

> Authenticated attackers can exploit SQL injection in the search field to retrieve all database data, including plaintext user credentials.

- **Severity:** High 7.3 (`CVSS:3.1/AV:A/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2025
- **Updated:** 26 Sep 2025
- **Also known as:** GHSA-m358-x52g-3qmx

## What is CVE-2025-59816?

CVE-2025-59816 is a high-severity SQL injection vulnerability in Zenitel ICX500, published on 25 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This vulnerability allows attackers to directly query the underlying database, potentially retrieving all data stored in the Billing Admin database, including user credentials. User passwords are stored in plaintext, significantly increasing the severity of this issue.

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

## Which versions are affected by CVE-2025-59816?


## How do I fix CVE-2025-59816?

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

## Is CVE-2025-59816 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59816 and fix it if it is affected.

What it is: CVE-2025-59816 is a high-severity SQL injection vulnerability in Zenitel ICX500, published on 25 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59816 in the wild and no public exploit code.

Affected product: Zenitel ICX500. 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-2025-59816/ (Markdown: https://insights.sbomify.com/CVE-2025-59816/index.md)
```

## Sources

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

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