CVE-2025-58780
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedindex.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."
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceSQL injection vulnerability in index.em7 component of ScienceLogic SL1 allows remote attackers to inject malicious SQL queries through unsanitized parameters in HTTP requests before version 12.1.1.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify ScienceLogic SL1 installationCheck for SL1 installation directories such as /opt/sciencelogic, /home/em7, or look for 'ScienceLogic' or 'SL1' processes running on the system using 'ps aux | grep -i sciencelogic' or 'systemctl list-units | grep -i em7'Affected if ScienceLogic SL1 is not found on the system (not affected)
-
Determine installed SL1 versionCheck version files in common SL1 directories such as /opt/sciencelogic/sl1/version, /home/em7/.version, or run 'rpm -q sciencelogic-sl1' or 'em7version' command if availableAffected if Version is present and is lower than 12.1.1 (potentially affected)
-
Verify index.em7 component is accessibleCheck if the web interface component index.em7 exists in the web root directory (typically under /opt/sciencelogic/em7/www/ or /home/em7/www/) and is exposed via the web serverAffected if index.em7 file exists and the web interface is externally accessible (potentially affected if version is below 12.1.1)
-
Check HTTP access logs for index.em7 requestsReview web server access logs (typically in /var/log/httpd/ or /opt/sciencelogic/em7/logs/) for requests to index.em7 and inspect query parameters for signs of SQL injection attemptsAffected if Unusual or malicious SQL syntax is observed in HTTP requests to index.em7 (indicates active exploitation attempts)
The environment is affected if ScienceLogic SL1 is installed with a version lower than 12.1.1 and the index.em7 web component is accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to ScienceLogic SL1 version 12.1.1 or later. If immediate upgrade is not feasible, implement input validation and parameterized queries as an interim control.
12.1.1
- Upgrade ScienceLogic SL1 to version 12.1.1 or later to remediate the SQL injection vulnerability in index.em7
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-58780 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-58780 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data