dbcve.org
OnbaseApplication · Hyland

CVE-2020-25251

CRITICAL · 9.1 CVSS v3.1 Published 2020-09-11
Fix available
A fix is available. Upgrade to after 20.3.10.1000 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
An 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. Client-side authentication is used for critical functions such as adding users or retrieving sensitive information.

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 confidence

Hyland OnBase uses client-side authentication validation for critical functions including user management and sensitive data retrieval. This allows attackers to bypass authentication by directly调用API endpoints or manipulating client-side validation, enabling unauthorized user creation and access to sensitive information without proper server-side authorization checks.

MitigationImplement server-side authentication and authorization checks for all critical functions. Ensure all API endpoints validate user credentials and permissions server-side before executing sensitive operations or returning sensitive data.

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
OnbaseApplication
Affected:<= 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.1000

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
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Hyland OnBase version
    Check the product version in the OnBase administration console or system information panel. The version is typically displayed in the About section or can be retrieved via the diagnostic tools provided by Hyland.
    Affected if The installed version falls within any of these ranges: <= 16.0.2.83; >= 17.0.0.0 and <= 17.0.2.109; >= 18.0.0.0 and <= 18.0.0.37; >= 19.0.0.0 and <= 19.8.16.1000; >= 20.0.0.0 and <= 20.3.10.1000
  2. Verify API endpoint exposure
    Review network traffic or API access logs for direct calls to OnBase API endpoints, particularly those related to user management (such as user creation or modification endpoints). Check if these endpoints can be accessed without proper authentication tokens.
    Affected if API endpoints related to user management or sensitive data retrieval are accessible without server-side authentication validation
  3. Inspect server-side authorization configuration
    Review the OnBase server configuration and web service settings to determine whether server-side authentication and authorization checks are enforced for all critical functions. Look for any configuration that relies solely on client-side validation.
    Affected if The configuration shows that critical API endpoints rely on client-side validation rather than server-side authorization checks for user management or sensitive data access

A user is affected if they are running any Hyland OnBase version within the affected ranges listed above AND their API endpoints can be accessed or manipulated without proper server-side authentication validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 20.3.10.1000
Interim mitigation

Implement server-side authentication and authorization checks for all critical functions. Ensure all API endpoints validate user credentials and permissions server-side before executing sensitive operations or returning sensitive data.

Recommended fix Moderate confidence

Contact Hyland for the latest patched version (patches are released per version branch - 16.x, 17.x, 18.x, 19.x, and 20.x)

  1. 1. Identify the current OnBase version in use from the Admin node or system information.
  2. 2. Determine which version branch (16.x, 17.x, 18.x, or 19.x) the current installation falls under.
  3. 3. Contact Hyland Software technical support to obtain the latest patched version for your specific release line, as patches are released per version branch.
  4. 4. Request and apply the security hotfix or patch that addresses CVE-2020-25251.
  5. 5. After patching, verify that client-side authentication is no longer used for critical functions by reviewing server-side authentication logs and configurations.
  6. 6. Test critical operations (adding users, retrieving sensitive information) to confirm proper server-side authentication is enforced.
Caveat Standard upgrade precautions apply - test in non-production environment first, backup configuration, and verify third-party integrations

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Onbase Scoped from the published advisory
  • Consultation12.0 h
  • Implementation60.0 h
  • Testing24.0 h
  • Review / QA16.0 h
112.0 hours of engineering $19,680
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $31,488.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-25251 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-25251 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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