dbcve.org
Infocage SiteshellApplication · Nec

CVE-2020-5632

HIGH · 7.8 CVSS v3.1 Published 2020-10-06
Fix available
A fix is available. Upgrade to 2.0.0.6 / 2.1.0.7 or later.
See remediation →
80/100
Remediation priority · High
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
InfoCage SiteShell series (Host type SiteShell for IIS V1.4, V1.5, and V1.6, Host type SiteShell for IIS prior to revision V2.0.0.6, V2.1.0.7, V2.1.1.6, V3.0.0.11, V4.0.0.6, V4.1.0.5, and V4.2.0.1, Host type SiteShell for Apache Windows V1.4, V1.5, and V1.6, and Host type SiteShell for Apache Windows prior to revision V2.0.0.6, V2.1.0.7, V2.1.1.6, V3.0.0.11, V4.0.0.6, V4.1.0.5, and V4.2.0.1) allow authenticated attackers to bypass access restriction and to execute arbitrary code with an elevated privilege via a specially crafted executable files.

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

InfoCage SiteShell series contains an access control bypass vulnerability where authenticated attackers can upload specially crafted executable files to bypass existing access restrictions and achieve arbitrary code execution with elevated privileges.

MitigationApply vendor patches for all affected versions (V1.4-V1.6 for IIS and Apache Windows, plus specific prior versions for V2.x, V3.x, and V4.x branches) to remediate the access control bypass and prevent privilege escalation.

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
Infocage SiteshellApplication
Affected:< 2.0.0.6>= 2.0.0.0, < 2.0.0.6>= 2.1.0.0, < 2.1.0.7>= 2.1.1.0, < 2.1.1.6>= 3.0.0.0, < 3.0.0.11>= 4.0.0.0, < 4.0.0.6>= 4.1.0.0, < 4.1.0.5>= 4.2.0.0, < 4.2.0.1= 1.4= 1.5= 1.6

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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/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 checks

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

  1. Identify if Nec Infocage Siteshell is installed
    Check the Windows program list (Add/Remove Programs or Programs and Features), or look for the installation directory typically under C:\Program Files\Nec\Infocage SiteShell or C:\Infocage\SiteShell
    Affected if Nec Infocage Siteshell is present on the system
  2. Determine the installed version number
    Locate the version information in the product's about dialog, readme file, or check the executable properties of the main Siteshell binary (typically named SiteShell.exe or similar)
    Affected if The version falls within any of these ranges: < 2.0.0.6, >= 2.0.0.0 and < 2.0.0.6, >= 2.1.0.0 and < 2.1.0.7, >= 2.1.1.0 and < 2.1.1.6, >= 3.0.0.0 and < 3.0.0.11, >= 4.0.0.0 and < 4.0.0.6, >= 4.1.0.0 and < 4.1.0.5, >= 4.2.0.0 and < 4.2.0.1, or equals 1.4, 1.5, or 1.6
  3. Verify the web upload interface is exposed
    Check if the Siteshell web management interface is accessible over HTTP/HTTPS (typically on ports 80, 443, or a custom port configured during installation)
    Affected if The web interface is reachable and allows authenticated access to file upload functionality
  4. Confirm authentication is enabled for upload features
    Review the Siteshell configuration to determine if the upload feature requires authentication and check if anonymous or low-privilege accounts can access it
    Affected if Authenticated users with upload permissions exist in the system, as the vulnerability exploits authenticated upload functionality to bypass access controls

A user is affected if Nec Infocage Siteshell is installed with a version matching any of the vulnerable ranges (V1.4-V1.6, V2.x prior to fixed versions, V3.x prior to 3.0.0.11, or V4.x prior to 4.0.0.6/4.1.0.5/4.2.0.1) and the web-based file upload interface is accessible to authenticated users.

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
Upgrade available Upgrade to 2.0.0.6 / 2.1.0.7 / 2.1.1.6 or later
Fixed in 2.0.0.62.1.0.72.1.1.6
Interim mitigation

Apply vendor patches for all affected versions (V1.4-V1.6 for IIS and Apache Windows, plus specific prior versions for V2.x, V3.x, and V4.x branches) to remediate the access control bypass and prevent privilege escalation.

Fix this in Infocage Siteshell Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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