/

CVE-2026-72595

Severity:

HIGH RISK

(8.1)

Broken Access Control (CWE-284) in Handesk Tickets

CVE-2026-72595

Deferred

Vulnerability type

Category:

Broken Access Control

CWE:

CWE-284

Impact:

Unauthorized modification of ticket records and cross-team data integrity compromise

Severity:

HIGH RISK

(8.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

A broken access control vulnerability in BadChoice Handesk may allow any authenticated agent to update tickets assigned to other teams. The issue becomes risky when the ticket update endpoint accepts requests without authorization or team-scoped ownership checks, enabling unauthorized modification, escalation, or corruption of ticket records.

Affected context

The vulnerability occurs in Handesk deployments where authenticated agents can reach the ticket update functionality and the application does not enforce authorization at the controller or service layer. Risk is present when ticket ownership, team assignment, or update permissions are not checked before changes are persisted.

Exploit preconditions

  • Attack surface: The ticket update endpoint handled by TicketsController@update
  • Required access: A valid authenticated agent account
  • Trigger point: Submission of an update request for a ticket associated with another team
  • Why exploitation is possible: The update path may omit both an authorization call and a team-scoped ownership check

Why this happens

The underlying bug is an authorization design failure: the application processes ticket updates based on authentication alone rather than verifying whether the authenticated agent is permitted to modify the specific record. This behavior maps to CWE-284: Improper Access Control, because access decisions do not adequately enforce object ownership, team boundaries, or role-based permissions.

Potential impact

  • An attacker may modify tickets assigned to other teams
  • Ticket priority, status, ownership, or content could be altered without approval
  • Unauthorized escalation of tickets could disrupt support workflows
  • Sensitive ticket information could be corrupted or indirectly exposed
  • Operational records and audit reliability may be weakened

General mitigation guidance

Mitigation generally focuses on enforcing authorization for every object-level update and reducing reliance on authentication alone.

Common defensive patterns include:

  • Applying centralized policy checks before loading or updating ticket records
  • Enforcing team-scoped ownership and role-based permissions server-side
  • Using deny-by-default authorization for cross-team operations
  • Validating that the requested ticket belongs to a team the agent may manage
  • Preventing clients from overriding protected ownership or team fields
  • Running application processes with only the database and service privileges they require
  • Logging authorization decisions and anomalous cross-team update attempts

How teams detect issues like this

Organizations commonly identify this class of issue through:

  • Static analysis and policy checks for update actions lacking authorization calls
  • Code review searches for controller methods that update records directly from request data
  • Tests using agents from different teams to verify object-level access boundaries
  • Dynamic testing of horizontal privilege escalation across ticket identifiers
  • Repository policies requiring authorization checks for create, read, update, and delete operations

Automated security review tools may help flag endpoints that lack visible permission enforcement, but business rules and team boundaries should also be tested explicitly.

Sources

SourceLink
github.comgithub.com/BadChoice/handesk

Frequently asked

questions

It may be exploitable through the application's ticket update interface when that endpoint is reachable by an authenticated agent.

The attacker generally needs a valid agent account. Administrative privileges or membership in the target team should not be necessary if team-scoped authorization is missing.

Enforce server-side, object-level authorization before every ticket update, including checks for the agent's role, team membership, and permitted fields.

Use centralized authorization policies, deny-by-default permissions, cross-team access tests, and code-review requirements for protected record operations.

Find out what's already
exploitable in your codebase.