CVE-2020-25252
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 through 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. CSRF can be used to log in a user, and then perform actions, because there are default credentials (the wstinol password for the manager or hsi account).
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 confidenceHyland OnBase contains a Cross-Site Request Forgery (CSRF) vulnerability that allows attackers to authenticate as a user and perform unauthorized actions. The vulnerability is exploitable due to the presence of default credentials (the wstinol password for the manager or hsi account), which can be leveraged in conjunction with CSRF to perform actions on behalf of authenticated users.
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
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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 the installed OnBase versionLocate the OnBase version information through the product's administration console, registry, or version file. Common locations include the application header, help menu, or installation directory.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
-
Verify if default wstinol password is changed for manager accountAccess the user management section of the OnBase administration interface and check whether the manager account is using a non-default password. Compare the current password configuration against the default wstinol credential.Affected if The manager account still uses the default wstinol password or the password has not been changed from its default value
-
Verify if default wstinol password is changed for hsi accountAccess the user management section of the OnBase administration interface and check whether the hsi account is using a non-default password. Compare the current password configuration against the default wstinol credential.Affected if The hsi account still uses the default wstinol password or the password has not been changed from its default value
-
Check for CSRF protection mechanismsInspect the OnBase web application configuration and HTTP responses to determine if CSRF tokens are implemented for state-changing requests, or if SameSite cookie attributes are configured.Affected if The application lacks CSRF token validation for sensitive operations and does not implement SameSite cookie attributes on session cookies
You are affected if your OnBase version is within the vulnerable ranges AND either default wstinol passwords remain active for manager/hsi accounts OR CSRF protections are missing from the application.
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 dataImmediately change the default wstinol password for the manager and hsi accounts, and update OnBase to a patched version. Implement CSRF tokens or same-site cookie attributes to prevent cross-site request forgery attacks.
- Consultation8.0 h
- Implementation16.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 $12,352.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25252 — 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-25252 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