dbcve.org
Modified Ecommerce ShopsoftwareApplication · Modified Shop

CVE-2017-8110

CRITICAL · 10.0 CVSS v3.1 Published 2017-04-25
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
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
www.modified-shop.org modified eCommerce Shopsoftware 2.0.2.2 rev 10690 has XXE in api/it-recht-kanzlei/api-it-recht-kanzlei.php.

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 confidence

XML External Entity (XXE) injection vulnerability in the it-recht-kanzlei API endpoint (api/it-recht-kanzlei/api-it-recht-kanzlei.php) of modified eCommerce Shopsoftware version 2.0.2.2 rev 10690 allows attackers to interfere with XML processing, potentially accessing local files or performing Server-Side Request Forgery (SSRF).

MitigationDisable external entity processing and XML entity expansion in the PHP XML parser configuration for the affected API endpoint, or implement proper input validation and sanitization for XML data.

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
Modified Ecommerce ShopsoftwareApplication
Affected:= 2.0.2.2

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
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/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 checks

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

  1. Verify the installed Modified eCommerce Shopsoftware version
    Check the version file or admin panel for the exact version number. Common locations include a version.php file in the includes/ directory or the admin backend system info page.
    Affected if The installed version is exactly 2.0.2.2 (rev 10690)
  2. Locate the it-recht-kanzlei API endpoint file
    Search for the file api/it-recht-kanzlei/api-it-recht-kanzlei.php in the web root directory.
    Affected if The file api/it-recht-kanzlei/api-it-recht-kanzlei.php exists on the server
  3. Confirm the API endpoint is accessible
    Attempt to access the URL path /api/it-recht-kanzlei/api-it-recht-kanzlei.php via HTTP request to verify the endpoint responds.
    Affected if The API endpoint is reachable and responds to requests

You are affected if you are running Modified eCommerce Shopsoftware version 2.0.2.2 (rev 10690) AND the api/it-recht-kanzlei/api-it-recht-kanzlei.php file exists and is accessible on your server.

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

Disable external entity processing and XML entity expansion in the PHP XML parser configuration for the affected API endpoint, or implement proper input validation and sanitization for XML data.

Fix this in Modified Ecommerce Shopsoftware Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,080
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2017-8110 — 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-8110 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