CVE-2019-15751
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 unrestricted file upload vulnerability in SITOS six Build v6.2.1 allows remote attackers to execute arbitrary code by uploading a SCORM file with an executable extension. This allows an unauthenticated attacker to upload a malicious file (containing PHP code to execute operating system commands) to the web root of the application.
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 confidenceSITOS six Build v6.2.1 contains an unrestricted file upload vulnerability that allows unauthenticated remote attackers to upload files with executable extensions (such as .php) by disguising them as SCORM files. Since uploaded files are stored in the web root, attackers can directly execute the malicious PHP code to achieve remote code 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= 6.2.1CVSS 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.1/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 installed Sitos Six versionLocate the Sitos Six application and check its build/version number. This is typically found in the application header, about page, or version information file within the installation directory.Affected if The installed version is exactly 6.2.1 (Sitos Six Build v6.2.1)
-
Verify SCORM upload functionality is accessibleDetermine if the SCORM file upload feature is enabled and accessible to users. Check the application's module configuration or feature flags related to SCORM content uploads.Affected if SCORM upload functionality is enabled and exposed to users (particularly unauthenticated users if the application permits this)
-
Inspect uploaded file storage locationExamine the application configuration or file system to determine where uploaded SCORM files are stored. Check if the storage path resolves to the web root directory.Affected if Uploaded files are stored within the web-accessible document root directory, allowing direct HTTP requests to reach them
-
Check file validation configuration for uploadsReview the application's upload handling configuration or code to identify what validation (if any) is performed on uploaded files, including MIME type checking, extension whitelist, and file content verification.Affected if No strict file type validation (MIME type whitelist and extension whitelist) is implemented for SCORM uploads, or validation can be bypassed by disguising file types
-
Verify uploaded files retain original extensionsCheck whether the application renames or modifies uploaded filenames during the upload process, or whether it preserves the original file extension.Affected if Uploaded files retain their original extensions, allowing executable extensions like .php to be preserved and stored in the web root
A user is affected if they are running Sitos Six version 6.2.1 with SCORM upload functionality enabled, storing files in the web root without strict extension/MIME type validation.
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 whitelist) for SCORM uploads, store uploaded files outside the web root, rename files upon upload to prevent executable extensions, and add content-type/header validation to verify actual file format.
- Consultation3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15751 — 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-15751 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