CVE-2019-13976
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 · uneditedeGain Chat 15.0.3 allows unrestricted file upload.
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 confidenceeGain Chat 15.0.3 contains an unrestricted file upload vulnerability that allows attackers to upload potentially malicious files without proper validation. This could enable remote code execution if executable or script-based files are uploaded and subsequently accessed.
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= 15.0.3CVSS 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.0/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 eGain Chat versionCheck the installed eGain Chat version by reviewing application files, configuration files, or the product's built-in version information (typically found in about pages, manifest files, or installer records).Affected if The installed version is exactly 15.0.3
-
Locate file upload functionalityIdentify where file upload capability exists in the eGain Chat deployment. Review web application configuration files, JSP/servlet definitions, or application logs that reference upload handlers or multipart request processors.Affected if File upload functionality is present and enabled in the deployment
-
Determine upload directory accessibilityReview web server configuration and application deployment descriptors to locate the configured upload directory. Verify if this directory is served by the web server or accessible via HTTP/HTTPS.Affected if The upload directory is web-accessible or within the webroot
-
Check file validation configurationInspect application configuration files (such as web.xml, application.properties, or custom upload handler configs) for file type validation settings. Look for allowed extensions, MIME type checks, or content validation logic.Affected if No file type validation, no extension checking, or no content-type validation is configured for uploads
-
Verify script execution settingsExamine the web server configuration (IIS web.config, Apache .htaccess, or similar) for the upload directory to determine if script execution is explicitly disabled.Affected if Script execution is not disabled in the upload directory and .jsp, .php, .asp, or similar executable extensions can be served
A user is affected if running eGain Chat version 15.0.3 with file upload functionality enabled and without proper validation or script execution restrictions on uploaded files.
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 file type validation (both MIME type and extension), validate file content/magic bytes, store uploads outside the webroot, rename uploaded files, and disable script execution in upload directories.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.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 $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-13976 — 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-2019-13976 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