CVE-2020-25247
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 18.0.0.32 and 19.x through 19.8.9.1000. Directory traversal exists for writing to files, as demonstrated by the FileName 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 confidenceHyland OnBase versions through 18.0.0.32 and 19.x through 19.8.9.1000 contain a directory traversal vulnerability in the FileName parameter that allows authenticated or unauthenticated attackers to write files to arbitrary locations on the host filesystem, potentially leading to remote code execution or configuration tampering.
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<= 18.0.0.32>= 19.0.0.0, <= 19.8.9.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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Hyland OnBase installationLook for OnBase services, web applications, or installation directories on the system. Check for IIS application pools named OnBase, or look in common installation paths such as C:\OnBase or C:\Program Files\Hyland.Affected if OnBase software is found on the system
-
Check installed version against affected rangesLocate the OnBase version information, typically found in the OnBase Administration module, in assembly version files within the installation directory, or in the Windows Registry under the OnBase service entries.Affected if The installed version is 18.0.0.32 or lower, OR between 19.0.0.0 and 19.8.9.1000 inclusive
-
Verify web interface accessibilityDetermine if the OnBase web client or API endpoints are exposed externally or accessible on the network. Check IIS or the web server configuration for OnBase web applications.Affected if The OnBase web interface is accessible (this makes the FileName parameter reachable)
-
Review logs for directory traversal attemptsExamine OnBase web server logs and IIS logs for requests containing '../' sequences in parameters, particularly looking for the FileName parameter with traversal patterns.Affected if Log entries show traversal patterns like '../' in the FileName parameter
-
Check for unauthorized file creationInspect web-accessible directories and system directories for unexpected or recently created files, especially in locations outside the typical OnBase data folders, such as web root directories or system folders.Affected if Files exist in unexpected locations or outside designated OnBase directories
A system is affected if Hyland OnBase is installed with a version in the affected ranges and the web interface is accessible, regardless of whether exploitation is observed.
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 patches for OnBase 18.0.0.32 and 19.8.9.1000. Additionally, implement strict input validation on the FileName parameter to enforce allowlist patterns and normalize file paths to prevent traversal sequences (../).
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-25247 — 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-25247 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