CVE-2025-58780
BaseFortify
Publication date: 2025-09-05
Last updated on: 2025-09-08
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| sciencelogic | sl1 | 12.1.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-58780 is a high-impact SQL injection vulnerability in ScienceLogic SL1 versions before 12.1.1, specifically in the index.em7 file. It allows an attacker to inject malicious SQL statements through a request parameter, which can lead to unauthorized manipulation of database queries, potentially granting unauthorized access to sensitive data or control over the database. The issue was discovered in 2023 and fixed in version 12.1.1. [1]
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute unauthorized SQL commands on the affected system's database, leading to unauthorized access to sensitive information or potential control over the database. This can compromise data confidentiality and integrity, potentially disrupting operations and exposing sensitive data to attackers. [1]
What immediate steps should I take to mitigate this vulnerability?
To mitigate the CVE-2025-58780 SQL injection vulnerability in ScienceLogic SL1, immediately upgrade your system to version 12.1.1 or later, as this version contains the fix for the vulnerability. Additionally, ensure that your SL1 agents are updated to the minimum required versions and follow best security practices such as validating TLS connections and using signed agent packages. [1, 2]