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

Q: How do I fix CVE-2016-10551?

waterline-sequel: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Q: Is CVE-2016-10551 being exploited?

CVE-2016-10551 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2016-10551 affect?

CVE-2016-10551 affects waterline-sequel. Severity is critical (CVSS 9.8). 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 co

Q: How urgent is CVE-2016-10551?

Priority 64/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

This week

CRITICAL 9.8REMOTEDOWNGRADE

CVE-2016-10551 is a critical-severity flaw (CVSS 9.8) affecting waterline-sequel. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

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.

Why this priority

Critical severity
Public exploit reference
Remotely exploitable, no login, no user action

No fix is published yet: follow the downgrade or mitigation steps.

Risk facts

CVSS score	9.8 (Critical)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	None
EPSS exploit chance	1.8% (top 22%)
CISA exploited list	No
Weakness	CWE-89
Published	2018-05-29
Last modified	2026-06-17

Publisher (CNA): HackerOne · Vendor: balderdash

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2018-05-29 20:29 UTCPublished CVE record published
2026-06-17 00:39 UTCUpdated Record last modified

balderdash waterline-sequel DOWNGRADE

Affected: 0.5.0

Fixed in: no fixed release known

Safe to downgrade to: a release before 0.5.0

1. Check installed version

npm ls waterline-sequel

2. No fixed release: DOWNGRADE to a release before 0.5.0

npm view waterline-sequel versions npm install waterline-sequel@"<0.5.0"

Downgrade risk

Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.

After downgrade

Restart the service, and keep the package held until a fixed release ships.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-10551?

waterline-sequel: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2016-10551 being exploited?

CVE-2016-10551 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-10551 affect?

CVE-2016-10551 affects waterline-sequel. Severity is critical (CVSS 9.8). 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 co

How urgent is CVE-2016-10551?

Priority 64/100. Critical severity; Public exploit reference; Remotely exploitable, no login, no user action

References

← Back to latest CVEs