SQL Injection in ScienceLogic SL1 index.em7
CVE-2025-58780 describes a reported SQL injection issue in ScienceLogic SL1 affecting versions before 12.1.1. According to the provided description, the vulnerable component is index.em7, which allegedly allows SQL injection via a request parameter. Successful exploitation would depend on unsafe incorporation of attacker-controlled input into backend SQL queries. The record explicitly notes that the supplier disputes the CVE description, stating that it inaccurately describes the vulnerability. No additional technical details about the specific parameter, code path, query construction, authentication requirements, or exploitability conditions were provided in the available content.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If the reported issue is valid, exploitation could allow an attacker to manipulate backend SQL queries executed by the application. Depending on the application's database permissions and the reachable query context, this could result in unauthorized access to data, modification or deletion of records, authentication bypass in some scenarios, or broader compromise of the affected application. However, the exact impact cannot be determined from the available information, and the supplier disputes the vulnerability description.
If you can’t patch tonight, do this now.
Until vendor-confirmed remediation is validated, reduce exposure to the affected index.em7 endpoint and any untrusted request parameters reaching it. Restrict network access to the SL1 interface to trusted administrative networks, enforce strong authentication and least-privilege access, monitor for anomalous requests indicative of SQL injection attempts, and deploy compensating controls such as WAF rules or input filtering where feasible. These are general mitigations for a suspected SQL injection condition; no vulnerability-specific workaround was provided in the available content.
Patch, then assume compromise.
Upgrade ScienceLogic SL1 to version 12.1.1 or later, as the issue is described as affecting versions before 12.1.1. Because the supplier disputes the published description, remediation should be validated against official ScienceLogic advisories, release notes, or support guidance to confirm the nature of the issue and the appropriate fix path.
No validated public exploits yet. Hidden: 1 rejected by Mallory's analysis as not a working exploit.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
3 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.