Vulnerabilities

Security incident · GHSA-jf75-q64q-g65r

Waline login accepts a non-string email as a match-all MongoDB query

Published Oct 28, 2026 · catalog updated Oct 28, 2026 · Waline login accepts a

Last checked Oct 30, 2026. A connected source was read within the last 7 days.

Open the advisory

Exploitation likelihood is not on this record for GHSA-jf75-q64q-g65r. A missing EPSS score is not a low risk. Compare Waline login accepts a with the linked advisory before you change production.

Severity

Medium6.5

Known exploitation

Not in CISA/VulnCheck KEV

EPSS

Awaiting synchronization with FIRST

Remediation

Version ranges on file

Affected products

npm @waline/vercel

## Summary The login endpoint POST /api/token reads the field from the request body without checking its type and passes it straight into the MongoDB storage query. When is not a string (for example a JSON object such as {"$ne": null}), the MongoDB storage adapter's parseWhere silently DROPS the field rather than rejecting the request, producing an empty filter that matches ALL users. The endpoint then verifies the submitted password against the FIRST user returned (user[0]), which in Waline is the first-registered user — the site administrator. This is a PARTIAL authentication bypass, not a full one. The attacker still needs a valid password for that first user; this is not a zero-knowledge bypass and it does not disclose passwords. Its concrete effects are: (1) the email/identifier factor is removed for the administrator account, (2) user enumeration (a non-string email never fails the "no such user" branch), and (3) credential-stuffing amplification — an attacker can test a leaked or weak password against the administrator account without knowing the administrator's email. ## Details Untyped input — packages/server/src/controller/token.js:17-18: email filter email email email password` as strings before they reach the storage query — for example in packages/server/src/logic/token.js postAction(): Defense in depth: in mongodb.js parseWhere(), reject (rather than silently drop) a value that is neither a string nor a supported array form, or coerce it to {$eq: String(value)}, so a non-string key can never elide the filter.