CVE-2019-15748
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 · uneditedSITOS six Build v6.2.1 permits unauthorised users to upload and import a SCORM 2004 package by browsing directly to affected pages. An unauthenticated attacker could use the upload and import functionality to import a malicious SCORM package that includes a PHP file, which could execute arbitrary PHP code.
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 lacks authentication controls on its SCORM 2004 package upload and import functionality, allowing unauthenticated attackers to directly access these pages. The system processes uploaded SCORM packages without adequate validation, enabling malicious packages containing PHP files to be uploaded and subsequently executed for arbitrary code execution.
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 application version number in the system administration panel, about page, or version file. Check the build information typically found under Help > About or in a version.ini file in the application root.Affected if The installed version is exactly 6.2.1 (no other versions are listed as affected)
-
Verify SCORM upload endpoint accessibilityAttempt to access the SCORM 2004 package upload and import URLs without providing any authentication credentials. Common paths include /scorm/upload, /scorm/import, /scorm2004/upload, or similar endpoints documented in the application's routing configuration.Affected if The upload/import pages load and accept requests without requiring login or returning an authentication error
-
Test SCORM package upload without authenticationSend a multipart form request to the identified SCORM upload endpoint with a valid SCORM package (ZIP file) to confirm the upload succeeds without session cookies or authentication headers.Affected if The upload completes successfully and returns a success response without any authentication requirement
-
Check file type validation on uploadsInspect the upload handling code or attempt to upload a file with a .php extension (or a ZIP containing PHP files) to the SCORM upload endpoint and observe whether the system accepts or rejects it.Affected if PHP files or other executable extensions are accepted and stored on the server without being blocked by file type validation
-
Verify PHP execution in upload directoryLocate the directory where SCORM packages are stored (typically /uploads, /scorm/packages, or similar) and check if PHP files placed there can be executed via HTTP request, or examine web server configuration for the upload directory.Affected if PHP files in the upload directory are executable when accessed via web browser (PHP execution is not disabled in that directory)
You are affected if your Sitos Six installation is version 6.2.1 AND the SCORM upload/import functionality is accessible without authentication AND PHP files can 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 dataImplement authentication and role-based authorization checks on all SCORM package upload/import endpoints, validate uploaded file types and contents to reject PHP files, and disable PHP execution in upload directories.
- Consultation4.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-15748 — 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-15748 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