# CVE-2025-58780: SQL injection in SL1

> An attacker can perform SQL injection via a request parameter in ScienceLogic SL1, potentially accessing or modifying data.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Sep 2025
- **Updated:** 8 Sep 2025
- **Also known as:** GHSA-cfrp-33c4-m9hw

## What is CVE-2025-58780?

CVE-2025-58780 is a high-severity SQL injection vulnerability in ScienceLogic SL1, published on 5 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

index.em7 in ScienceLogic SL1 before 12.1.1 allows SQL Injection via a parameter in a request. NOTE: this is disputed by the Supplier because it "inaccurately describes the vulnerability."

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

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


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

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

## Is CVE-2025-58780 being exploited?

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

Public exploit code:

- SQLi in ScienceLogic (github_poc): https://github.com/SexyShoelessGodofWar/CVE-2025-58780

## Fix prompt for AI coding agents

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

What it is: CVE-2025-58780 is a high-severity SQL injection vulnerability in ScienceLogic SL1, published on 5 Sep 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-58780 exists.

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

## Sources

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

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