LiveActive security incident?Get immediate response
CVE Record

CVE-2016-10551: waterline-sequel is a module that helps generate SQL statements for Waterline apps Any user input that goes...

waterline-sequel is a module that helps generate SQL statements for Waterline apps Any user input that goes into Waterline's `like`, `contains`, `startsWith`, or `endsWith` will end up in waterline-sequel with the potential for malicious code. A malicious user can input their own SQL statements in waterline-sequel 0.50 that will get executed and have full access to the database.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysishigh

Security readout for executives and security teams

Plain-English summary

This CVE describes SQL injection in the waterline-sequel Node module. If an application using version 0.5.0 passes untrusted input into certain Waterline search filters, that input may be executed as SQL, potentially exposing or modifying the full database.

Executive priority

Treat as high priority for any internet-facing application using the affected module, because successful exploitation could compromise database confidentiality and integrity. If the dependency is absent, business urgency drops sharply.

Technical view

waterline-sequel 0.5.0 can mishandle user input passed through Waterline like, contains, startsWith, or endsWith criteria. The CVE maps this to CWE-89 and states malicious SQL can be executed with full database access. No CVSS score or fixed version is provided in the bundle.

Likely exposure

Exposure is likely limited to applications using waterline-sequel 0.5.0, especially Sails/Waterline-backed services that expose searchable fields to users through the affected query operators.

Exploitation context

The bundle does not show CISA KEV listing or confirmed active exploitation. The vulnerability is still serious because ordinary search or filtering inputs may become database-executed SQL when routed through affected Waterline criteria.

Researcher notes

The source bundle identifies one affected version and vulnerable operator paths but does not provide CVSS, exploit maturity, or a named fixed release. Validate exposure through dependency evidence and data-flow review rather than assuming all Waterline usage is affected.

Mitigation direction

  • Inventory applications for waterline-sequel 0.5.0.
  • Check Waterline, NodeSecurity, and package maintainer guidance for fixed versions.
  • Upgrade or remove the vulnerable dependency where vendor guidance supports it.
  • Restrict untrusted input from affected Waterline operators until remediated.
  • Add server-side validation for searchable user-supplied fields.

Validation and detection

  • Review dependency manifests and lockfiles for waterline-sequel 0.5.0.
  • Search application code for like, contains, startsWith, and endsWith criteria.
  • Trace public API parameters into Waterline query construction paths.
  • Run safe regression tests confirming special characters remain data.
  • Review database logs for unusual queries from affected search endpoints.
Prepared
Confidence
medium
Sources
4

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-89: Database access and collection lookup

Injection into data stores can inform collection, data access, and exfiltration detection reviews. 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

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-2016-10551 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
3Source 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
HackerOnewaterline-sequel node module0.5.0Listed
Weakness

CWE details

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

CWE-89 · source CWE mapping

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection')

Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.