CVE-2020-25143
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 · uneditedAn issue was discovered in Observium Professional, Enterprise & Community 20.8.10631. It is vulnerable to SQL Injection due to the fact that it is possible to inject malicious SQL statements in malformed parameter types. This can occur via /ajax/device_entities.php?entity_type=netscalervsvr&device_id[]= because of /ajax/device_entities.php.
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 · high confidenceSQL Injection vulnerability in Observium through /ajax/device_entities.php. The device_id[] parameter (and possibly entity_type) accepts malformed input that is not properly sanitized before being used in SQL queries, allowing attackers to inject arbitrary SQL statements.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data= 20.8.10631CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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.
-
Locate Observium installationSearch for Observium web application files on the system, typically installed in /var/www/html/ or similar web root directories. Look for the observium directory structure.Affected if Observium is installed on the system
-
Identify installed Observium versionCheck the version file or footer in the Observium web interface, or look for a version identifier in the installation directory. Common locations include version.php or a VERSION file in the root observium folder.Affected if Installed version is 20.8.10631
-
Verify affected file existsCheck if the file /ajax/device_entities.php exists in the Observium web directory. This is the file containing the SQL injection vulnerability.Affected if The file /ajax/device_entities.php exists in the Observium installation
-
Confirm AJAX endpoint is accessibleVerify the /ajax/device_entities.php endpoint is reachable via HTTP/HTTPS from the web server. Attempt to access the URL or check web server configuration for allowed routes.Affected if The AJAX endpoint is accessible via the web server
-
Check if device_id parameter handling is enabledReview the device_entities.php code to confirm the device_id[] parameter is processed without input validation or parameterized queries. This typically requires code review of the affected file.Affected if The device_id[] parameter is processed without proper input sanitization or prepared statements
The environment is affected if Observium version 20.8.10631 is installed and the /ajax/device_entities.php file is accessible with the device_id[] parameter accepting unsanitized input.
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.
From vendor dataApply input validation and use parameterized queries/prepared statements for all database operations in device_entities.php. Upgrade to patched version if available.
- Consultation3.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,168.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25143 — 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-2020-25143 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