CVE-2020-13887
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 · unediteddocuments_add.php in Kordil EDMS through 2.2.60rc3 allows Remote Command Execution because .php files can be uploaded to the documents folder.
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 confidenceThe documents_add.php endpoint in Kordil EDMS versions up to 2.2.60rc3 lacks proper file upload validation, allowing attackers to upload executable .php files to a web-accessible documents folder. Once uploaded, these files can be requested directly to achieve Remote Command Execution on the server.
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< 2.2.60= 2.2.60CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 Kordil EDMS installation and versionLocate the Kordil EDMS installation directory and check version files or headers. Common locations include the web root or /var/www/html/. Look for version indicators in source files or configuration.Affected if The installed version is less than 2.2.60 or equals 2.2.60 (versions up to and including 2.2.60rc3 are affected)
-
Verify documents_add.php endpoint existsCheck if the file documents_add.php exists within the Kordil EDMS web accessible directory structure. This is typically found in the main application folder.Affected if The endpoint file exists and is accessible via HTTP
-
Confirm upload directory is web-accessibleExamine the Kordil EDMS configuration or upload handler code to determine where uploaded files are stored. Check if this directory is accessible via the web server (within the document root).Affected if Uploads are stored in a directory reachable via HTTP/HTTPS
-
Test for unrestricted PHP file uploadAttempt to upload a test file with .php extension through the documents_add.php endpoint (or examine the upload validation logic in the source code if direct testing is not permitted).Affected if Files with .php extension are accepted and stored in a web-accessible location
-
Check if uploaded PHP files are executableRequest the uploaded test file via HTTP to determine if the web server executes it as PHP code.Affected if The uploaded .php file is served as executable content rather than being downloaded or blocked
A user is affected if they run Kordil EDMS version 2.2.60 or earlier, the documents_add.php endpoint exists, and the upload directory is web-accessible allowing PHP files to be uploaded and executed.
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 data2.2.60
Implement strict file upload validation (disallow .php extensions, validate MIME types and file content) and either store uploads outside the web root or disable script execution in the upload directory using web server configuration.
- Consultation6.0 h
- Implementation12.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 $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13887 — 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-13887 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