/

CVE-2026-36102

Severity:

HIGH RISK

(7.2)

Improper Privilege Management (CWE-269) in Checkmate

CVE-2026-36102

Deferred

Vulnerability type

Category:

Improper Privilege Management

CWE:

CWE-269

Impact:

Privilege Escalation

Severity:

HIGH RISK

(7.2)

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

Bluewave Labs Checkmate contains an improper privilege management issue in its invite controller. An authenticated administrator may manipulate the role parameter on the invite endpoint to obtain superadmin-level privileges.

Affected context

The issue occurs in the inviteController.js component and affects Checkmate deployments using the /api/v1/invite endpoint. Risk exists when an authenticated administrator can submit invite requests whose role value is accepted without sufficiently restricting assignable privileges.

Exploit preconditions

  • Attack surface: The authenticated /api/v1/invite API endpoint
  • Required access: A valid administrator account
  • Trigger point: Processing the role parameter in an invite request
  • Why exploitation is possible: The endpoint may permit an administrator-controlled role value to assign privileges beyond the administrator's authorized level

Why this happens

The underlying bug is improper privilege management, mapped to CWE-269. The application appears to trust a caller-controlled role parameter during invitation or account provisioning without enforcing a server-side authorization boundary that prevents lower-privileged administrators from granting superadmin access.

Potential impact

  • An authenticated administrator could obtain superadmin privileges
  • Unauthorized users could receive elevated privileges through manipulated invitations
  • Security and administrative controls could be altered
  • Sensitive application data or functionality may be accessed
  • The affected tenant or deployment could experience broader administrative compromise

General mitigation guidance

Mitigation generally focuses on enforcing authorization independently of request parameters.

Common defensive patterns include:

  • Apply server-side allowlists for roles that each administrator may assign
  • Prevent administrator-controlled input from granting roles above the caller's effective privilege
  • Enforce centralized authorization checks for invitation and account-provisioning actions
  • Treat role values as untrusted input and validate them against the authenticated principal's permissions
  • Use least-privilege defaults for newly invited accounts
  • Record and review changes involving privileged roles

How teams detect issues like this

Detection approaches may include:

  • Static analysis and code review for authorization decisions based directly on request role parameters
  • Checks that compare assignable roles with the authenticated caller's effective privilege
  • API policy rules restricting superadmin assignment to explicitly authorized principals
  • Monitoring for administrator accounts creating or assigning superadmin roles
  • Audit review of invitation events, role changes, and unexpected privilege transitions

Automated security review tools can help identify missing authorization checks around role-management endpoints.

Sources

SourceLink
gist.github.comgist.github.com/Joren2087/cc60f1c8dfe0680c1e5e867b70703e22
outline.joren2087.beoutline.joren2087.be/s/f02631bd-cddd-4e59-952b-0e756cdc8fba

Frequently asked

questions

Exploitation requires an authenticated administrator account capable of reaching the affected invite endpoint.

No. The described attack requires authentication as an administrator, although the resulting privilege increase may broaden access significantly.

Enforce server-side authorization for every assignable role and ensure that a caller cannot grant privileges higher than those they are permitted to delegate.

Use centralized access-control policies, least-privilege defaults, strict role allowlists, and audit monitoring for privileged account and invitation changes.

Find out what's already
exploitable in your codebase.