CVE-2026-111640
Received Received - Intake

DooTask Missing Authorization in WebSocketDialog

Vulnerability report for CVE-2026-111640, including description, CVSS score, EPSS score, affected products, exploitability, helpful resources, and attack-flow context.

Publication date: 2026-10-16

Last updated on: 2026-10-16

Assigner: VulnCheck

Description

DooTask through 1.9.66 contains a missing authorization vulnerability in WebSocketDialog::checkDialog() that skips the membership check for dialogs with group_type 'okr'. Authenticated users can supply the dialog_id of OKR comment dialogs to msg__list, msg__one, or msg__send* endpoints to read and inject messages.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-10-16
Last Modified
2026-10-16
Generated
2026-10-16
AI Q&A
2026-10-16
EPSS Evaluated
N/A
NVD
EUVD

Affected Vendors & Products

Showing 1 associated CPE
Vendor Product Version / Range
kuaifan dootask 0

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-639 The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-111640 is a missing authorization vulnerability in DooTask versions up to 1.9.66. The WebSocketDialog::checkDialog() function fails to verify membership for OKR comment dialogs, allowing authenticated users to access these dialogs by providing a dialog_id to endpoints like msg__list, msg__one, or msg__send*. Users can then read existing messages or inject new ones into private OKR discussions they are not part of.

The flaw occurs because the code has a special branch for OKR dialogs that skips the standard membership check applied to other dialog types. This bypasses intended access controls, enabling unauthorized data exposure and manipulation.

Detection Guidance

Check for unauthorized access to OKR comment dialogs by monitoring WebSocket traffic or application logs for requests to msg__list, msg__one, or msg__send* endpoints with dialog_id parameters. Look for unusual message injections or reads in OKR discussions.

Impact Analysis

If you use DooTask 1.9.66 or earlier, an attacker with valid credentials could access private OKR discussions by guessing or obtaining dialog IDs. They may read sensitive project goals, key results, or internal communications. Attackers could also inject misleading or malicious messages into these discussions, potentially disrupting workflows or spreading misinformation.

Since OKR dialogs are meant to be private to specific teams, this vulnerability could lead to unauthorized access to strategic planning information, affecting decision-making processes and organizational transparency.

Compliance Impact

This vulnerability could lead to unauthorized access to sensitive project data, which may include personal or confidential information. For GDPR, this could result in violations of data protection principles if personal data is exposed without authorization. For HIPAA, if the application handles protected health information within OKR discussions, unauthorized access could breach compliance requirements.

Organizations using DooTask for regulated data must address this vulnerability to avoid potential fines, legal liabilities, and reputational damage associated with non-compliance with data protection regulations.

Mitigation Strategies

Upgrade DooTask to a patched version beyond 1.9.66. If unavailable, apply a temporary fix by modifying WebSocketDialog.php to enforce membership checks for OKR dialogs. Restrict access to sensitive dialogs and review logs for suspicious activity.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-111640. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart