LiveActive security incident?Get immediate response
CVE Record

CVE-2018-3754: Node.js third-party module query-mysql versions 0.0.0, 0.0.1, and 0.0.2 are vulnerable to an SQL injection...

Node.js third-party module query-mysql versions 0.0.0, 0.0.1, and 0.0.2 are vulnerable to an SQL injection vulnerability due to lack of user input sanitization. This may allow an attacker to run arbitrary SQL queries when fetching data from database.

UnknownCVSS not scoredNot KEV-listedUpdated
Discuss exposureBack to CVEs
Glexia's TakeAutomated analysisunknown

Security readout for executives and security teams

Plain-English summary

CVE-2018-3754 affects the Node.js third-party module query-mysql versions 0.0.0 through 0.0.2. The reported issue is SQL injection caused by insufficient user input sanitization, which could let an attacker run arbitrary database queries. The sources do not provide a CVSS score, named affected products, or confirmed exploitation.

Executive priority

Treat this as a targeted dependency exposure check rather than a broad emergency. Prioritize systems that use old Node.js dependencies and connect to customer, payment, authentication, or operational databases.

Technical view

The vulnerable component is query-mysql, a Node.js module. Versions 0.0.0, 0.0.1, and 0.0.2 reportedly fail to sanitize user input before database access, creating SQL injection risk when fetching data. Public source details are sparse and do not identify a fixed version, CPEs, or exploit activity.

Likely exposure

Exposure is likely limited to Node.js applications that directly depend on query-mysql 0.0.0, 0.0.1, or 0.0.2 and pass user-controlled data into database fetch paths. The CVE record lists no broader product or platform impact.

Exploitation context

The source bundle does not show CISA KEV listing or other cited evidence of active exploitation. The practical risk depends on whether vulnerable query-mysql code is reachable from untrusted input and connected to sensitive databases.

Researcher notes

Public evidence is limited to the CVE record and HackerOne reference. The title and description identify affected module versions and vulnerability class, but do not provide scoring, exploit status, affected CPEs, or a named patched release.

Mitigation direction

  • Inventory applications and lockfiles for query-mysql versions 0.0.0, 0.0.1, or 0.0.2.
  • Check maintainer or vendor guidance before assuming a fixed replacement version exists.
  • Remove or replace vulnerable usage where no supported fixed release is available.
  • Use parameterized database queries and server-side validation around affected code paths.
  • Limit database privileges used by affected applications.

Validation and detection

  • Review dependency manifests and deployed artifacts for vulnerable query-mysql versions.
  • Identify whether user-controlled input reaches query-mysql database fetch operations.
  • Check application and database logs for unusual query patterns around exposed endpoints.
  • Confirm database accounts used by the app have least-privilege permissions.
  • Document findings because the public CVE data lacks CVSS, CPEs, and fixed-version detail.
Prepared
Confidence
medium
Sources
3

Public sources used

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

Database behavior lookup

The CVE wording references database injection or access, so collection and exfiltration 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-3754 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.