LiveActive security incident?Get immediate response
CVE Record

CVE-2020-18166: Unrestricted File Upload in LAOBANCMS v2.0 allows remote attackers to upload arbitrary files by attaching a...

Unrestricted File Upload in LAOBANCMS v2.0 allows remote attackers to upload arbitrary files by attaching a file with a ".jpg.php" extension to the component "admin/wenjian.php?wj=../templets/pc".

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2020-18166 is a reported unrestricted file upload issue in LAOBANCMS v2.0. A remote attacker may be able to upload an arbitrary file through an administrative file component. If that uploaded file is served or executed by the web server, business impact could include site compromise and data exposure.

Executive priority

Treat this as a high-priority exposure review if LAOBANCMS is in use, especially on internet-facing systems. The absence of CVSS and patch data lowers certainty, not potential impact.

Technical view

The source describes insufficient upload validation in LAOBANCMS v2.0, specifically the admin file handling component. The reported bypass involves accepting a file with a double extension associated with server-side execution. No CVSS score, CWE, vendor advisory, fixed version, or official mitigation is provided in the bundle.

Likely exposure

Exposure is most likely where LAOBANCMS v2.0 is deployed and the affected administrative upload component is reachable. Public internet exposure would increase urgency. The source bundle does not identify CPEs, package names, or broader affected versions.

Exploitation context

The CVE is not listed as CISA KEV in the provided bundle, and no cited source states active exploitation. The public reference contains vulnerability details, so defenders should assume the issue is discoverable, but exploitation in the wild is not evidenced here.

Researcher notes

The public data is sparse: one CVE description and one GitHub reference. Validate product identity, deployment path, authentication requirements, and server execution behavior before assigning final risk. Do not assume other versions are affected without additional evidence.

Mitigation direction

  • Inventory any LAOBANCMS deployments and confirm whether v2.0 is present.
  • Check vendor or project guidance for a fixed version or official workaround.
  • Limit administrative interface access to trusted networks or authenticated administrators.
  • Review upload handling for executable double-extension files and unsafe destinations.
  • Harden web server behavior so uploaded content is not executed.

Validation and detection

  • Confirm whether LAOBANCMS v2.0 exists in production, staging, or legacy environments.
  • Check whether the administrative file upload component is reachable externally.
  • Review web-accessible upload directories for unexpected executable files.
  • Inspect web server logs for unusual upload activity involving double extensions.
  • Verify any vendor patch or workaround after applying it.
Prepared
Confidence
medium
Sources
3

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2020-18166 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
2Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.