# CVE-2026-61518: ISPConfig Authenticated SQL Injection via Remote API primary_id Parameter

> Authenticated attackers can inject SQL via the Remote API to read or modify database records across all tenants.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **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:** 19 Aug 2026
- **Updated:** 20 Aug 2026
- **Also known as:** GHSA-m99h-35x2-cjq2

## What is CVE-2026-61518?

CVE-2026-61518 is a high-severity SQL injection vulnerability in ispconfig3, published on 19 Aug 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ISPConfig contains an authenticated SQL injection vulnerability in the Remote API. The primary_id parameter passed to delete and update API methods is concatenated directly into SQL WHERE clauses without integer casting or parameterized query binding. The built-in SQL injection scanner does not block quote-free boolean payloads and does not reject requests in its default configuration. A remote API user holding any single low-privilege function permission can inject arbitrary SQL to delete or modify records across all tenants in the control panel database and extract arbitrary data via blind boolean inference, including password hashes and client records.

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

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


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

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

## Is CVE-2026-61518 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-61518 is a high-severity SQL injection vulnerability in ispconfig3, published on 19 Aug 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-61518 exists.

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

## Sources

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

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