CVE-2017-10886
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 · uneditedCross-site scripting vulnerability in CS-Cart Japanese Edition v4.3.10 and earlier (excluding v2 and v3), CS-Cart Multivendor Japanese Edition v4.3.10 and earlier (excluding v2 and v3) allows an attacker to inject arbitrary web script or HTML 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 confidenceCross-site scripting (XSS) vulnerability in CS-Cart Japanese Edition and CS-Cart Multivendor Japanese Edition v4.3.10 and earlier allows attackers to inject arbitrary web script or HTML via unspecified vectors. This is a stored XSS flaw likely in user-supplied input fields that are not properly sanitized before display.
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= 4.0.1= 4.0.2= 4.0.3= 4.1.1= 4.1.2= 4.1.3= 4.1.4= 4.2.1= 4.2.2= 4.2.3= 4.2.4= 4.3.1= 4.0.1= 4.0.2= 4.0.3= 4.1.1= 4.1.2= 4.1.3= 4.1.4= 4.2.1= 4.2.2= 4.2.3= 4.2.4= 4.3.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
- Low
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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.
-
Locate CS-Cart installation directoryIdentify the web root directory where CS-Cart is installed. Common paths include /var/www/html/, /home/user/public_html/, or the document root of your web server.Affected if CS-Cart files are present in the identified directory
-
Find the version fileIn the CS-Cart root directory, look for a version.php, config.php, or similar file that contains the application version. Alternatively, access the admin panel and navigate to Administration > Cache or the system information page.Affected if A version file exists and displays a version number
-
Compare installed version to affected versionsRead the version number from the version file or admin panel. Compare it against the affected versions: 4.0.1, 4.0.2, 4.0.3, 4.1.1, 4.1.2, 4.1.3, 4.1.4, 4.2.1, 4.2.2, 4.2.3, 4.2.4, 4.3.1 (or any version 4.3.10 and earlier per the summary).Affected if The installed version matches or is earlier than the versions listed in the affected range
-
Confirm Japanese Edition variantCheck if the installation is the Japanese Edition of CS-Cart or CS-Cart Multivendor Japanese Edition. This may be indicated in the product name displayed in the admin panel, or in configuration files that specify the edition type.Affected if The installation is confirmed as CS-Cart Japanese Edition or CS-Cart Multivendor Japanese Edition
You are affected if your CS-Cart installation is the Japanese Edition (or Multivendor Japanese Edition) and the installed version is 4.3.10 or earlier, particularly matching versions 4.0.1 through 4.3.1.
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 CS-Cart Japanese Edition/Multivendor Japanese Edition to a version beyond v4.3.10, or apply vendor-provided patches. Implement input validation and output encoding for all user-supplied data displayed in the application.
- Consultation3.0 h
- Implementation6.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-10886 — 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-10886 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