dbcve.org
Soy CmsApplication · N I Agroinformatics

CVE-2017-2163

HIGH · 7.5 CVSS v3.0 Published 2017-05-12
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
Directory traversal vulnerability in SOY CMS Ver.1.8.1 to Ver.1.8.12 allows authenticated attackers to read arbitrary files via shop_id.

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 confidence

Directory traversal vulnerability in SOY CMS versions 1.8.1 through 1.8.12 allows authenticated attackers to read arbitrary files on the server by manipulating the shop_id parameter with path traversal sequences (e.g., ../../../). This enables unauthorized access to sensitive configuration files, source code, or system files outside the intended web root.

MitigationUpdate SOY CMS to a version beyond 1.8.12. Alternatively, implement strict input validation and path canonicalization on the shop_id parameter to reject traversal sequences, and ensure the web application runs with minimal file system privileges.

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
Soy CmsApplication
Affected:= 1.8.1= 1.8.2= 1.8.3= 1.8.4= 1.8.5= 1.8.6= 1.8.7= 1.8.8= 1.8.9= 1.8.10= 1.8.11= 1.8.12

CVSS 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
None
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify SOY CMS installation and version
    Locate the SOY CMS installation directory and check the version file or metadata. Common locations include the root directory where version.php, version.txt, or similar version information may be stored. Check the version number against the affected range: 1.8.1 through 1.8.12.
    Affected if The installed version of SOY CMS is 1.8.1, 1.8.2, 1.8.3, 1.8.4, 1.8.5, 1.8.6, 1.8.7, 1.8.8, 1.8.9, 1.8.10, 1.8.11, or 1.8.12.
  2. Determine if shop module is enabled
    Check the SOY CMS configuration or module settings to verify whether the shop/e-commerce functionality is installed and active. Look for shop-related directories, configuration files, or admin panel settings that indicate the shop module is enabled.
    Affected if The shop module is enabled and accessible in the SOY CMS installation.
  3. Verify authentication requirements
    Review the shop functionality to confirm it requires authentication. The vulnerability requires an authenticated attacker to exploit the shop_id parameter. Check if user accounts with shop access exist and whether the login mechanism is active.
    Affected if User authentication is configured for the shop module, meaning an attacker with valid credentials could attempt exploitation.
  4. Inspect network exposure of shop functionality
    Examine the web server configuration and SOY CMS routing to determine if the shop functionality is accessible over the network. Check for URL patterns involving shop_id parameter in the web application.
    Affected if The shop functionality is accessible via HTTP/HTTPS requests, exposing the vulnerable parameter.

You are affected if SOY CMS version 1.8.1 through 1.8.12 is installed with the shop module enabled and accessible, allowing authenticated users to manipulate the shop_id parameter with path traversal sequences.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update SOY CMS to a version beyond 1.8.12. Alternatively, implement strict input validation and path canonicalization on the shop_id parameter to reject traversal sequences, and ensure the web application runs with minimal file system privileges.

Fix this in Soy Cms Scoped from the published advisory
  • Consultation4.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,840
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,544.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-2163 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2017-2163 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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