CVE-2026-55369 (GCVE-0-2026-55369)
Vulnerability from cvelistv5 – Published: 2026-10-28 12:56 – Updated: 2026-10-28 12:56| URL | Tags |
|---|---|
| https://github.com/walinejs/waline/security/advis… | x_refsource_CONFIRM |
| https://github.com/walinejs/waline/pull/3646 | x_refsource_MISC |
| https://github.com/walinejs/waline/commit/e611aed… | x_refsource_MISC |
{
"containers": {
"cna": {
"affected": [
{
"product": "waline",
"vendor": "walinejs",
"versions": [
{
"status": "affected",
"version": "\u003c= 1.40.3"
}
]
}
],
"descriptions": [
{
"lang": "en",
"value": "Waline is a comment system with backend support. Prior to version 1.41.1, the login endpoint POST /api/token reads the email field from the request body without checking its type and passes it straight into the MongoDB storage query. When email is not a string (for example a JSON object such as {\"$ne\": null}), the MongoDB storage adapter\u0027s 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 \u2014 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 \u2014 an attacker can test a leaked or weak password against the administrator account without knowing the administrator\u0027s email. This issue has been patched in version 1.41.1."
}
],
"metrics": [
{
"cvssV3_1": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
"version": "3.1"
}
}
],
"problemTypes": [
{
"descriptions": [
{
"cweId": "CWE-287",
"description": "CWE-287: Improper Authentication",
"lang": "en",
"type": "CWE"
}
]
},
{
"descriptions": [
{
"cweId": "CWE-943",
"description": "CWE-943: Improper Neutralization of Special Elements in Data Query Logic",
"lang": "en",
"type": "CWE"
}
]
}
],
"providerMetadata": {
"dateUpdated": "2026-10-28T12:56:15.822Z",
"orgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"shortName": "GitHub_M"
},
"references": [
{
"name": "https://github.com/walinejs/waline/security/advisories/GHSA-jf75-q64q-g65r",
"tags": [
"x_refsource_CONFIRM"
],
"url": "https://github.com/walinejs/waline/security/advisories/GHSA-jf75-q64q-g65r"
},
{
"name": "https://github.com/walinejs/waline/pull/3646",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/walinejs/waline/pull/3646"
},
{
"name": "https://github.com/walinejs/waline/commit/e611aed4e571c2a86103f5cee48791ca6b460360",
"tags": [
"x_refsource_MISC"
],
"url": "https://github.com/walinejs/waline/commit/e611aed4e571c2a86103f5cee48791ca6b460360"
}
],
"source": {
"advisory": "GHSA-jf75-q64q-g65r",
"discovery": "UNKNOWN"
},
"title": "Waline login accepts a non-string email as a match-all MongoDB query"
}
},
"cveMetadata": {
"assignerOrgId": "a0819718-46f1-4df5-94e2-005712e83aaa",
"assignerShortName": "GitHub_M",
"cveId": "CVE-2026-55369",
"datePublished": "2026-10-28T12:56:15.822Z",
"dateReserved": "2026-06-16T18:57:40.181Z",
"dateUpdated": "2026-10-28T12:56:15.822Z",
"state": "PUBLISHED"
},
"dataType": "CVE_RECORD",
"dataVersion": "5.2",
"vulnerability-lookup:meta": {
"epss": {
"cve": "CVE-2026-55369",
"date": "2026-10-30",
"epss": "0.00262",
"percentile": "0.18089"
},
"nvd": {
"cve": {
"affected": [
{
"affectedData": [
{
"product": "waline",
"vendor": "walinejs",
"versions": [
{
"status": "affected",
"version": "\u003c= 1.40.3"
}
]
}
],
"source": "security-advisories@github.com"
}
],
"cveTags": [],
"descriptions": [
{
"lang": "en",
"value": "Waline is a comment system with backend support. Prior to version 1.41.1, the login endpoint POST /api/token reads the email field from the request body without checking its type and passes it straight into the MongoDB storage query. When email is not a string (for example a JSON object such as {\"$ne\": null}), the MongoDB storage adapter\u0027s 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 \u2014 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 \u2014 an attacker can test a leaked or weak password against the administrator account without knowing the administrator\u0027s email. This issue has been patched in version 1.41.1."
}
],
"id": "CVE-2026-55369",
"lastModified": "2026-10-28T15:24:56.033",
"metrics": {
"cvssMetricV31": [
{
"cvssData": {
"attackComplexity": "LOW",
"attackVector": "NETWORK",
"availabilityImpact": "NONE",
"baseScore": 6.5,
"baseSeverity": "MEDIUM",
"confidentialityImpact": "LOW",
"integrityImpact": "LOW",
"privilegesRequired": "NONE",
"scope": "UNCHANGED",
"userInteraction": "NONE",
"vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N",
"version": "3.1"
},
"exploitabilityScore": 3.9,
"impactScore": 2.5,
"source": "security-advisories@github.com",
"type": "Secondary"
}
]
},
"published": "2026-10-28T13:17:08.120",
"references": [
{
"source": "security-advisories@github.com",
"url": "https://github.com/walinejs/waline/commit/e611aed4e571c2a86103f5cee48791ca6b460360"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/walinejs/waline/pull/3646"
},
{
"source": "security-advisories@github.com",
"url": "https://github.com/walinejs/waline/security/advisories/GHSA-jf75-q64q-g65r"
}
],
"sourceIdentifier": "security-advisories@github.com",
"vulnStatus": "Deferred",
"weaknesses": [
{
"description": [
{
"lang": "en",
"value": "CWE-287"
},
{
"lang": "en",
"value": "CWE-943"
}
],
"source": "security-advisories@github.com",
"type": "Primary"
}
]
}
}
}
}
Drag nodes to arrange them. Double-click a related vulnerability to open it, or a source to visit its link. The Physics button on the left tunes the layout and the simulation; the legend at the bottom left hides or shows nodes by kind and by sighting type.
Sightings
| Author | Source | Type | Date | Other |
|---|
Nomenclature
- Seen: The vulnerability was mentioned, discussed, or observed by the user.
- Confirmed: The vulnerability has been validated from an analyst's perspective.
- Published Proof of Concept: A public proof of concept is available for this vulnerability.
- Exploited: The vulnerability was observed as exploited by the user who reported the sighting.
- Patched: The vulnerability was observed as successfully patched by the user who reported the sighting.
- Not exploited: The vulnerability was not observed as exploited by the user who reported the sighting.
- Not confirmed: The user expressed doubt about the validity of the vulnerability.
- Not patched: The vulnerability was not observed as successfully patched by the user who reported the sighting.
Vulnerability timeline
Sightings and recorded dates, grouped by day · UTC
How durations are calculated
Following the VTEM framework (Black Hat USA 2015), time to patch starts when the vendor or a coordinator was informed, total time to patch at discovery, and disclosure to patch at public disclosure; vendor response time runs from the report to its acknowledgement. Time to exploit and time unpatched start at the earliest discovery or report, falling back to public disclosure. Unpatched time ends at the first recorded patch, or the calculation time when no patch is recorded. Exploitation to patch shows the interval between those two events; a published proof of concept is a public exploit, not exploitation.
Each result shows its source dates. A negative interval means the end event came first; when date-only inputs leave the order open, the result says so. Date-only inputs are approximate. The earliest evidence wins: KEV report dates and sightings are labelled as such. Records describing another vulnerability are listed but never calculated from, and a PoC alone does not establish exploitation. Missing patch evidence does not prove that no patch exists. Filters below change the event list only.
Loading timeline…
The approach is described in our paper Mapping CVEs to MITRE ATT&CK Techniques: A Curated Gold-Set Classifier and the Limits of LLM-Assisted Label Expansion.
Browse all ATT&CK techniques and the vulnerabilities related to each.
Related by attack behaviour
Vulnerabilities whose description is nearest to this one in the vector space of the CIRCL/vulnerability-attack-technique-biencoder model. This is a similarity search over the bi-encoder space (plain cosine), not a classification, and it has no measured accuracy.