CVE-2026-61518
Authenticated SQL injection in ISPConfig Remote API allows tenant-wide data theft and modification.
Is CVE-2026-61518 being exploited?
Not confirmed. CVE-2026-61518 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.31% probability of exploitation in the next 30 days.
How severe is CVE-2026-61518?
CVE-2026-61518 is rated High. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-61518?
Not known from our data. No patch reference has been recorded for CVE-2026-61518, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2026-61518 affect?
CVE-2026-61518 affects ISPConfig (Remote API). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-61518?
Restrict/disable Remote API access, apply vendor patch when released, rotate credentials and audit DB access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Authenticated SQLi via API primary_id lets low-privilege users extract DB data (password hashes, client records) and delete/modify records across all tenants.
Immediate action required
- affected>= 3.2.0 and <= *
- affected>= 3.3.0 and <= *
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.