CVE-2020-25253
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 the TableName, ColumnName, Name, UserId, or Password parameter.
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 document management system allows remote attackers to execute arbitrary SQL commands through multiple parameters (TableName, ColumnName, Name, UserId, Password) in versions 16.x through 20.x. The critical CVSS 9.8 score indicates network-exploitable, low-complexity attack requiring no authentication.
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 Hyland OnBase installation versionCheck the Windows registry key HKLM\SOFTWARE\Hyland\OnBase\Version or inspect the version info in the OnBase application administration console under System Administration > DiagnosticsAffected if The version displayed matches any of the affected ranges: <= 16.0.2.83, 17.0.0.0 through 17.0.2.109, 18.0.0.0 through 18.0.0.37, 19.0.0.0 through 19.8.16.1000, or 20.0.0.0 through 20.3.10.1000
-
Confirm OnBase Web Server or API components are exposedIdentify if the OnBase web interface (typically on ports 80/443 or custom ports) is accessible from the network by reviewing firewall rules, IIS bindings, or load balancer configurationsAffected if The OnBase web application is reachable from network segments accessible to potential attackers
-
Locate OnBase API endpoint configurationExamine IIS or the OnBase web server configuration files for exposed API paths that handle the TableName, ColumnName, Name, UserId, and Password parameters mentioned in the vulnerabilityAffected if API endpoints accepting these parameters are present in the exposed web application configuration
If the installed OnBase version falls within the affected ranges AND the web/API interface is network-accessible, the environment is vulnerable to CVE-2020-25253.
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 · scopedApply vendor patches to upgrade to fixed versions (16.0.2.84+, 17.0.2.110+, 18.0.0.38+, 19.8.16.1001+, 20.3.10.1001+) and refactor affected code paths to use parameterized queries instead of dynamic SQL construction.
Upgrade to the latest stable OnBase release (20.3.x or later) or to the first fixed release above your current affected version branch - contact Hyland Customer Portal for exact version numbers
- 1. Identify the currently installed OnBase version by checking the application server or consulting the Hyland console
- 2. Based on the affected version range (16.0.2.83 and below, 17.0.2.109 and below, 18.0.0.37 and below, 19.8.16.1000 and below, 20.3.10.1000 and below), determine the appropriate upgrade path for your major version line
- 3. Contact Hyland Software directly or access the Hyland Customer Portal to obtain the specific fixed release for your version
- 4. Schedule a maintenance window and perform a full backup of the OnBase database and configuration files
- 5. Apply the upgrade following Hyland's standard upgrade documentation for your version
- 6. Verify the SQL injection vulnerability is resolved by testing the affected parameters (TableName, ColumnName, Name, UserId, Password) or by confirming the patch level in the Hyland console
- 7. After upgrade, validate that all OnBase services start correctly and core functionality works as expected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25253 — 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-25253 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