/

CVE-2026-85395

Severity:

HIGH RISK

(7.1)

Missing Authorization (CWE-862) in UnoPim Admin ACL

CVE-2026-85395

Deferred

Vulnerability type

Category:

Missing Authorization

CWE:

CWE-862

Impact:

Privilege Escalation and Unauthorized API Access

Severity:

HIGH RISK

(7.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

UnoPim before 2.1.3 does not include integration store, update, and key-generation routes in its access-control map. An authenticated user with minimal administrative privileges may bypass authorization checks, create OAuth API integrations, mint client credentials, and potentially obtain higher-level access.

Affected context

The vulnerability occurs in UnoPim administrative functionality when integration-related routes are not represented in the ACL map used by the Bouncer authorization middleware. Deployments may be exposed when a low-privilege administrative account can reach these routes and the middleware relies on incomplete route-to-permission mappings.

Exploit preconditions

  • Attack surface: Administrative web or API routes for integration management
  • Required access: An authenticated account with minimal administrative privileges
  • Trigger point: Requests to integration store, update, or OAuth key-generation endpoints
  • Why exploitation is possible: The affected routes are absent from the ACL map, allowing requests to bypass expected permission validation

Why this happens

The underlying bug is an incomplete authorization policy map. Because integration management and credential-generation routes are omitted from the Bouncer middleware's ACL configuration, authorization decisions are not consistently applied to those operations. This behavior maps to CWE-862: Missing Authorization, where a protected function can be reached without an effective permission check.

Potential impact

  • A low-privilege administrator may create unauthorized OAuth API integrations
  • Attackers may mint client credentials with broader access than intended
  • Account or tenant privileges could be escalated
  • Unauthorized API activity could expose or modify protected data
  • Compromised credentials could support persistence or lateral access

General mitigation guidance

Mitigation generally focuses on making authorization explicit, centralized, and fail-closed.

Common defensive patterns include:

  • Registering every sensitive route and operation in a complete ACL or policy model
  • Denying access by default when a route lacks an authorization rule
  • Enforcing permission checks at the service or controller boundary rather than relying only on route metadata
  • Separating integration administration and credential-generation privileges
  • Limiting the scope and lifetime of issued OAuth credentials
  • Applying least privilege to administrative roles and service accounts
  • Reducing trust in client-supplied role or permission context

How teams detect issues like this

Organizations can identify similar authorization gaps through:

  • Static analysis and route inventory checks that compare sensitive endpoints with ACL or policy definitions
  • Code review checks for newly added routes without corresponding authorization rules
  • Tests that exercise each administrative endpoint with multiple privilege levels
  • Negative authorization tests confirming that unmapped or unknown routes are denied
  • Runtime monitoring for unexpected integration creation, key generation, or privilege changes
  • Policy enforcement requiring security review for credential-management functionality

Sources

SourceLink
github.comgithub.com/geo-chen/oss/blob/main/unopim.md
github.comgithub.com/unopim/unopim
github.comgithub.com/unopim/unopim/blob/v2.1.2/packages/Webkul/User/src/Http/Middleware/Bouncer.php
github.comgithub.com/unopim/unopim/commit/acbf2e160ced78446d6e4267e89f264bf04612c4
github.comgithub.com/unopim/unopim/releases/tag/v2.1.3
vulncheck.comvulncheck.com/advisories/unopim-before-2.1.3-missing-authorization-on-integration-management-routes

Frequently asked

questions

It may be exploitable through UnoPim's administrative web or API interface when the attacker can authenticate with a minimally privileged administrative account.

The attacker generally needs valid credentials for an account that can reach the affected integration routes. Anonymous access is not implied by the vulnerability description.

Ensure every integration and credential-management operation has an explicit permission check and that unmapped routes fail closed rather than being treated as allowed.

Maintain a complete route-to-permission inventory, use least-privilege roles, and include automated positive and negative authorization tests for every sensitive endpoint.

Find out what's already
exploitable in your codebase.