Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-72588: CWE-204: Observable Response Discrepancy in bluewave-labs Checkmate

0
Medium
Published: 08/10/2026 (08/10/2026, 12:31:53 UTC)
Source: CVE Database V5
Vendor/Project: bluewave-labs
Product: Checkmate

Description

A user enumeration vulnerability in bluewave-labs/Checkmate through 2.1.0 allows an unauthenticated remote attacker to determine whether a given email address is registered. The POST /api/v1/auth/recovery/request endpoint returns HTTP 200 for registered email addresses and a different status code for unregistered ones, enabling attackers to enumerate valid user accounts.

CVSS v3.1

Score 5.3medium

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 08/10/2026, 11:12:34 UTC

Technical Analysis

The vulnerability exists in the POST /api/v1/auth/recovery/request endpoint of bluewave-labs Checkmate up to version 2.1.0. When a request is made with a registered email address, the server responds with HTTP 200, whereas a different status code is returned for unregistered emails. This observable response discrepancy allows an unauthenticated attacker to enumerate valid user accounts by testing email addresses against this endpoint.

Potential Impact

An attacker can confirm the existence of user accounts by sending requests to the recovery endpoint and analyzing the HTTP status codes. This information disclosure can facilitate targeted phishing, social engineering, or brute force attacks. However, the vulnerability does not allow direct compromise of accounts or system integrity.

Mitigation Recommendations

Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, consider implementing uniform response codes for the recovery endpoint to prevent user enumeration. No official fix or temporary mitigation is currently documented.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
TuranSec
Date Reserved
2026-08-10T10:32:53.854Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 6a79ae70bf8831d5398afd4e

Added to database: 08/10/2026, 10:56:48 UTC

Last enriched: 08/10/2026, 11:12:34 UTC

Last updated: 08/10/2026, 21:20:35 UTC

Views: 8

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses