CVE-2017-14050
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 · uneditedIn BlackCat CMS 1.2, backend/addons/install.php allows remote authenticated users to execute arbitrary PHP code via a ZIP archive that contains a .php file.
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 confidenceIn BlackCat CMS 1.2, the backend/addons/install.php endpoint allows authenticated users to upload addon packages as ZIP archives. The vulnerability exists because the application does not properly validate the contents of uploaded ZIP archives before extraction, allowing malicious PHP files to be uploaded and subsequently executed 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= 1.2CVSS 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.0/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.
-
Confirm BlackCat CMS versionCheck the installed version by inspecting the CMS core files, typically found in a version.php or config file at the root of the BlackCat CMS installation. Look for a version constant or variable set to 1.2.Affected if The installed version is exactly 1.2 (BlackCat Cms Blackcat Cms: = 1.2)
-
Verify backend/addons/install.php existsCheck if the file backend/addons/install.php exists within the BlackCat CMS web root directory. This is the vulnerable endpoint for addon package uploads.Affected if The file backend/addons/install.php exists and is accessible via the web server
-
Confirm addon installation feature is accessibleLog into the BlackCat CMS backend and navigate to the addons section to verify the addon installation functionality is enabled and accessible to authenticated users.Affected if The addon installation feature is enabled and accessible to authenticated users without additional restrictions
-
Check upload directory permissionsInspect the directory where uploaded addon packages are extracted, typically within the BlackCat CMS addons or temp directory. Verify write permissions allow file extraction.Affected if The upload/extraction directory is writable and accessible from the web root, allowing extracted PHP files to be executed
A user is affected if they are running BlackCat CMS version 1.2, the backend/addons/install.php endpoint exists, the addon installation feature is accessible to authenticated users, and the extraction directory is writable within the web root.
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 dataRestrict addon installation to trusted administrators only and implement strict validation of ZIP archive contents—whitelist allowed file extensions and verify that no .php files are present in uploaded archives before extraction. Consider storing uploaded files outside the webroot.
- Consultation3.0 h
- Implementation6.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,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-14050 — 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-2017-14050 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