LiveActive security incident?Get immediate response
CVE Record

CVE-2018-3730: mcstatic node module suffers from a Path Traversal vulnerability due to lack of validation of filePath, whi...

mcstatic node module suffers from a Path Traversal vulnerability due to lack of validation of filePath, which allows a malicious user to read content of any file with known path.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

CVE-2018-3730 affects the mcstatic Node module. The published record says all versions allow path traversal because filePath is not properly validated, letting a malicious user read files when the path is known. This can expose secrets if the module serves files from a production host.

Executive priority

Treat this as a targeted exposure review, not an emergency internet-wide incident. Prioritize systems where mcstatic is internet-facing or runs near credentials, configuration files, or customer data.

Technical view

The issue is classified as CWE-22 path traversal. The source record describes insufficient validation of filePath in mcstatic, allowing arbitrary file content reads by known path. The bundle does not provide CVSS scoring, a fixed version, or detailed vendor remediation.

Likely exposure

Exposure is likely limited to applications that install and use the mcstatic Node module to serve files. The source says all versions are affected, but it does not identify downstream products or deployment prevalence.

Exploitation context

The provided sources do not state active exploitation, and the CVE is not marked as KEV. Exploitation would require reachability of vulnerable mcstatic file-serving behavior and knowledge or guessing of target file paths.

Researcher notes

Evidence is sparse. The CVE record identifies all versions of mcstatic and the root cause, but lacks CVSS, fixed-version, and exploit-in-the-wild details. Avoid assuming package maintenance status without checking current package/vendor data.

Mitigation direction

  • Inventory applications and containers for the mcstatic Node module.
  • Check current vendor or npm guidance for fixed, deprecated, or replacement package status.
  • If no maintained fixed version exists, plan migration away from mcstatic.
  • Restrict deployed file-serving components to non-sensitive directories and least-privilege runtime accounts.
  • Review logs for suspicious requests targeting sensitive local file paths.

Validation and detection

  • Search dependency manifests and lockfiles for mcstatic.
  • Confirm whether mcstatic routes are reachable from untrusted users.
  • Review application code for user-controlled filePath handling.
  • Verify runtime hosts do not expose secrets readable by the app process.
  • Document findings because no CVSS or fixed version is provided in the source bundle.
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.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
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-2018-3730 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
HackerOnemcstatic node moduleAll versionsListed
Weakness

CWE details

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

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.