CVE-2020-25260
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 remote attackers to execute arbitrary code because of unsafe JSON deserialization.
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 confidenceHyland OnBase document management system contains an unsafe JSON deserialization vulnerability affecting versions 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. Attackers can exploit this deserialization flaw to achieve remote code execution on affected systems.
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 installationCheck for OnBase installation directories, services, or applications on the system. Look for the 'OnBase' service or application pool in Windows services or IIS if hosted on a Windows server.Affected if OnBase software is present on the system
-
Determine installed OnBase versionLocate the OnBase version information, typically found in the application UI under Help/About, in installation logs, or in registry keys under the Hyland OnBase installation directory. Compare the installed version to the affected ranges: 16.0.2.83 and below, 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.Affected if The installed version falls within any of the affected version ranges
-
Identify exposed OnBase web servicesReview IIS or web server configuration to determine which OnBase endpoints and web services are externally accessible or exposed to untrusted networks. Check for API endpoints that handle JSON input.Affected if OnBase web services accepting JSON requests are exposed to network access
-
Verify if deserialization features are enabledCheck OnBase configuration settings related to JSON deserialization or object serialization. Review the application configuration files (such as web.config) for settings that control deserialization behavior.Affected if JSON deserialization or object serialization features are enabled in the OnBase configuration
You are affected if Hyland OnBase is installed and the installed version falls within the affected ranges (16.0.2.83 and below, 17.0.2.109 and below, 18.0.0.37 and below, 19.8.16.1000 and below, or 20.3.10.1000 and below) with exposed JSON-handling endpoints.
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 or upgrade to a patched OnBase version beyond the affected version ranges. Network segmentation and input validation can provide interim defensive measures.
- Consultation4.0 h
- Implementation8.0 h
- Testing16.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,576.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25260 — 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-25260 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