CVE-2017-2090
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 · uneditedDirectory traversal vulnerability in CubeCart versions prior to 6.1.4 allows remote authenticated attackers to read arbitrary files via unspecified vectors.
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 confidenceDirectory traversal vulnerability in CubeCart e-commerce platform versions prior to 6.1.4 allows authenticated remote attackers to escape the intended directory context and read arbitrary files on the server filesystem via path traversal sequences (e.g., '../' in user-supplied input), potentially exposing sensitive configuration files, credentials, or application source code.
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.1.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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/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 installed CubeCart versionLocate the version number in the CubeCart admin dashboard (usually under 'Maintenance' or 'System' > 'Version') or check the '/includes/extra/version.php' file if it exists in your installationAffected if Installed version is 6.1.3 or earlier (any version below 6.1.4)
-
Verify authenticated user access existsConfirm that the CubeCart installation has user accounts enabled and that there are registered users with login credentialsAffected if User authentication is enabled and there are active user accounts in the system
-
Check for file handling functionalityIdentify if any admin or user-accessible features allow file path input, such as image upload, file inclusion, or document retrieval functionsAffected if Any functionality that accepts file paths or allows file inclusion is accessible to authenticated users without proper validation
-
Inspect input validation on path parametersReview application code or test file-related requests with path traversal sequences (e.g., '../') in parameters that handle file pathsAffected if The application accepts and processes '../' sequences in user-supplied file path parameters without rejecting or sanitizing them
-
Confirm vulnerability trigger conditionSubmit an authenticated request containing path traversal sequences (such as ../../) in parameters used for file operations to observe if arbitrary file retrieval occursAffected if Authenticated users can escape the intended directory context and read files outside the web root using path traversal sequences
You are affected if your CubeCart version is 6.1.3 or earlier and authenticated users can access file handling functionality that does not reject path traversal sequences in file path parameters.
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 dataUpgrade CubeCart to version 6.1.4 or later to obtain the vendor patch. Additionally, implement strict input validation to reject path traversal sequences in all user-controllable file path parameters.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-2090 — 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-2090 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