CVE-2020-25254
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 Hyland OnBase 16.0.2.83 and below, 17.0.2.109 and below, 18.0.0.37 and below, 19.8.16.1000 and below and 20.3.10.1000 and below. It allows SQL injection, as demonstrated by TestConnection_LocalOrLinkedServer, CreateFilterFriendlyView, or AddWorkViewLinkedServer.
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 Hyland OnBase versions 16.x through 20.x allows attackers to inject malicious SQL queries through the TestConnection_LocalOrLinkedServer, CreateFilterFriendlyView, and AddWorkViewLinkedServer API methods. The lack of proper input sanitization in these methods enables unauthenticated remote attackers to manipulate database queries.
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<= 16.0.2.83>= 17.0.0.0, <= 17.0.2.109>= 18.0.0.0, <= 18.0.0.37>= 19.0.0.0, <= 19.8.16.1000>= 20.0.0.0, <= 20.3.10.1000CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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.
-
Identify installed OnBase versionLocate the OnBase version information through the Hyland product licensing portal, the OnBase Configuration application, or the Windows Programs and Features list. Compare the full version number (for example, 18.0.0.25) against the affected ranges: <= 16.0.2.83; 17.0.0.00 through 17.0.2.109; 18.0.0.00 through 18.0.0.37; 19.0.0.00 through 19.8.16.1000; or 20.0.0.00 through 20.3.10.1000.Affected if The installed version falls within any of the listed affected ranges.
-
Confirm API endpoint exposureDetermine whether the OnBase Application Server API endpoints are exposed to the network. The vulnerable methods are TestConnection_LocalOrLinkedServer, CreateFilterFriendlyView, and AddWorkViewLinkedServer. These are typically accessed through the OnBase API (often at paths like /api/ or /OnBaseAPI/) on the application server.Affected if The OnBase API endpoints are reachable from network locations where untrusted users could send requests.
-
Verify unauthenticated access to OnBase APICheck whether the OnBase Application Server permits unauthenticated access to the API methods. By default, OnBase requires authentication, but the SQL injection flaw allows injection through the named methods without proper input sanitization.Affected if The API accepts requests without requiring authentication, or authentication can be bypassed for the affected methods.
The environment is affected if the installed OnBase version falls within any of the specified vulnerable version ranges AND the API endpoints are network-accessible to unauthenticated users.
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 vendor-supplied patches for the specific OnBase version (16.0.2.84+, 17.0.2.110+, 18.0.0.38+, 19.8.16.1001+, 20.3.10.1001+). As interim mitigation, restrict network access to the OnBase application server and implement WAF rules to detect SQL injection patterns.
- Consultation8.0 h
- Implementation24.0 h
- Testing12.0 h
- Review / QA8.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $14,656.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25254 — 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-25254 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