Description
WhaTicket Community through commit cf04795 contains an insecure direct object reference vulnerability that allows authenticated agents to access other agents' tickets because ShowTicketService performs no ownership or queue checks. Attackers can supply another agent's ticket id to GET /tickets/:ticketId and /messages/:ticketId to read full message history and POST WhatsApp replies.
Published: 2026-10-16
Score: 5.3 Medium
EPSS: n/a
KEV: No
Impact: Unauthorized data access via IDOR (CWE‑639)
Action: Apply Patch
AI Analysis

Impact

The vulnerability is an insecure direct object reference (CWE‑639) that allows an authenticated agent to retrieve or manipulate data owned by other agents. The ShowTicketService performs no ownership or queue checks, enabling any authenticated user to supply a different ticket identifier and access the full message history or post replies via WhatsApp. This results in a confidentiality breach where ticket and message content intended for one agent becomes available to another.

Affected Systems

Canove Whaticket Community applications that incorporate commit cf04795 are affected. The CNA does not list specific version numbers; the flaw exists in any release that contains that commit. Operators should verify whether their deployed code base includes the commit or is newer, and consider updating to a version that implements ticket ownership checks.

Risk and Exploitability

The CVSS score of 5.3 indicates moderate severity. The EPSS score is not available, and the vulnerability is not listed in the CISA KEV catalog. Attackers only need valid agent credentials to exploit the flaw; they may send a GET request to /tickets/:ticketId or /messages/:ticketId or a POST reply endpoint with another agent’s ticket ID. The lack of ownership checks makes the exploitation route straightforward and possible in any environment where agents have access to the application.

Generated by OpenCVE AI on October 16, 2026 at 19:19 UTC.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to a Canove Whaticket Community release that implements ownership or queue checks on ticket and message endpoints; check the project repository for a newer commit addressing the IDOR protection.
  • If an immediate upgrade is not possible, implement a middleware or service‑level check that verifies the ticket owner matches the authenticated agent before returning data or accepting POST requests to reply endpoints.
  • Review role‑based access permissions so that only agents belonging to the appropriate queue or department can call ticket‑related APIs, reducing the attack surface.

Generated by OpenCVE AI on October 16, 2026 at 19:19 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories yet.

History

Fri, 16 Oct 2026 17:45:00 +0000

Type Values Removed Values Added
Description WhaTicket Community through commit cf04795 contains an insecure direct object reference vulnerability that allows authenticated agents to access other agents' tickets because ShowTicketService performs no ownership or queue checks. Attackers can supply another agent's ticket id to GET /tickets/:ticketId and /messages/:ticketId to read full message history and POST WhatsApp replies.
Title WhaTicket Community through commit cf04795 IDOR via /tickets/:ticketId and /messages/:ticketId
Weaknesses CWE-639
References
Metrics cvssV3_1

{'score': 5.4, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N'}

cvssV4_0

{'score': 5.3, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N'}


Subscriptions

No data.

cve-icon MITRE

Status: PUBLISHED

Assigner: VulnCheck

Published:

Updated: 2026-10-16T17:39:59.914Z

Reserved: 2026-10-16T14:31:22.961Z

Link: CVE-2026-111709

cve-icon Vulnrichment

No data.

cve-icon NVD

Status : Deferred

Published: 2026-10-16T18:17:55.070

Modified: 2026-10-16T19:03:18.127

Link: CVE-2026-111709

cve-icon Redhat

No data.

cve-icon OpenCVE Enrichment

Updated: 2026-10-16T19:30:13Z

Weaknesses
  • CWE-639

    Authorization Bypass Through User-Controlled Key