CVE-2020-13888
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 · uneditedKordil EDMS through 2.2.60rc3 allows stored XSS in users_edit.php, users_management_edit.php, and user_management.php.
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 confidenceStored cross-site scripting (XSS) vulnerability in Kordil EDMS user management modules (users_edit.php, users_management_edit.php, user_management.php) allows authenticated attackers to inject malicious JavaScript that executes in browsers of other users accessing these pages.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 Kordil EDMS installationLook for the Kordil EDMS application on the web server. Check for the presence of files like users_edit.php, users_management_edit.php, or user_management.php in the web root or a known Kordil EDMS directory.Affected if The application files exist on the server.
-
Determine installed versionLocate the version file or configuration within the Kordil EDMS installation. Common locations include a version.php file, a config file, or the application footer/admin panel. Compare the found version to the affected range: < 2.2.60 or = 2.2.60.Affected if The installed version is less than 2.2.60 or exactly 2.2.60.
-
Verify user management module is accessibleConfirm the affected files (users_edit.php, users_management_edit.php, user_management.php) are present in the deployment and accessible via the web server. Check if the user management functionality is enabled.Affected if The vulnerable user management PHP files are present and reachable via HTTP/HTTPS.
-
Confirm authentication is required or enabledReview the application's authentication configuration. Determine whether the user management pages require valid user credentials for access, or if anonymous access is permitted.Affected if The user management module accepts authenticated user input that gets stored and displayed to other users.
The environment is affected if Kordil EDMS is installed with version less than 2.2.60 or exactly 2.2.60, and the user management module is accessible to authenticated users who can input data that gets displayed without output encoding.
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 input validation and output encoding/escaping for all user-supplied data displayed in user management pages to prevent script execution.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-13888 — 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-13888 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