CVE-2020-5614
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 · uneditedDirectory traversal vulnerability in KonaWiki 3.1.0 and earlier allows remote attackers to read arbitrary files via unspecified vectors.
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 confidenceDirectory traversal vulnerability in KonaWiki 3.1.0 and earlier allows remote authenticated or unauthenticated attackers to read arbitrary files on the server by manipulating file paths using '..' sequences in unspecified input vectors.
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<= 3.1.0CVSS 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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 the installed KonaWiki versionLocate the version information in the application - check the main PHP files, an about page, or a configuration file that displays the software version. Compare the found version against the affected range: versions 3.1.0 and earlier.Affected if The installed version is 3.1.0 or any version number lower than 3.1.0.
-
Confirm network accessibility of the web applicationDetermine if the KonaWiki instance is accessible over the network by attempting to access its URL or checking firewall rules and network configurations that allow external connections.Affected if The application is reachable from remote locations (the vulnerability can be exploited by remote attackers).
-
Verify if file-related functionality is exposedIdentify any features in the application that accept file paths or perform file operations - look for parameters that might accept file names, paths, or attachments. Test whether these parameters are accessible without authentication or with standard user credentials.Affected if File path parameters are accessible without authentication or with any user account, making the directory traversal exploit possible.
-
Test for directory traversal vulnerabilityIf file path parameters are identified, attempt to access system files using '../' sequences in the input - for example, try to traverse to /etc/passwd or other sensitive files outside the intended upload or data directory.Affected if The application allows '..' sequences in input parameters and returns contents of files outside the intended directory, confirming the vulnerability is present and exploitable.
If the installed KonaWiki version is 3.1.0 or earlier and the application is network-accessible with file path functionality exposed, the environment is affected by CVE-2020-5614.
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 dataImplement strict input validation and sanitization for all file path parameters, ensuring path traversal sequences are blocked or normalized and restrict file access to intended directories.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-5614 — 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-5614 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