/

CVE-2026-71505

Severity:

HIGH RISK

(7.1)

Broken Object Authorization (CWE-639) in Dolibarr API

CVE-2026-71505

Deferred

Vulnerability type

Category:

Broken Object-Level Authorization

CWE:

CWE-639

Impact:

Unauthorized Account Access and Data Exposure

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

Dolibarr's REST API may fail to enforce per-company authorization on third-party account write routes. An authenticated user with permission to create third parties could change another company's WebPortal password, potentially access its invoice data, and receive the prior password verifier in the API response.

Affected context

The issue can arise in Dolibarr deployments that expose the REST API third-party site account write routes and grant users permission to create third-party records. Risk is higher when write operations do not apply the same object-level ownership or authorization checks used by corresponding read operations, and when API responses disclose sensitive authentication material.

Exploit preconditions

  • Attack surface: REST API routes that modify third-party site account or WebPortal credentials
  • Required access: An authenticated account with third-party creation rights
  • Target condition: A victim company must be addressable through the affected write operation
  • Trigger point: Processing a write request for a company account
  • Why exploitation is possible: Per-object authorization checks may be applied to read routes but omitted or inconsistently applied to write routes

Why this happens

The underlying flaw is an authorization design inconsistency in which an API verifies a user's general capability to perform an operation but does not sufficiently verify access to the specific company object being modified. This is a form of CWE-639: Authorization Bypass Through User-Controlled Key, commonly associated with insecure direct object references and broken object-level authorization. Returning a previous password verifier in the same response can further expose sensitive authentication data.

Potential impact

  • An attacker could change a victim company's WebPortal password
  • An attacker may authenticate as the affected company
  • Unauthorized access to the company's invoice data could occur
  • The previous password verifier could be exposed through the API response
  • Account integrity and tenant isolation could be weakened

General mitigation guidance

Mitigation generally focuses on enforcing object-level authorization consistently for every read and write operation.

Common defensive patterns include:

  • Authorizing the requested company object before applying any account or credential change
  • Deriving permitted object scope from the authenticated session rather than trusting client-supplied identifiers
  • Applying deny-by-default policies and explicit tenant-boundary checks to write routes
  • Removing password verifiers and other authentication secrets from API responses
  • Separating credential-management permissions from general third-party creation rights
  • Requiring reauthentication or stronger authorization for sensitive credential changes
  • Recording and monitoring changes to account credentials and object ownership

How teams detect issues like this

Organizations can look for this class of issue through:

  • Static analysis and code review checks for object identifiers used without nearby authorization enforcement
  • Comparisons between authorization logic on read and write handlers for the same resource
  • API tests that attempt cross-company access using accounts with limited object scope
  • Schema and response reviews that identify password hashes, verifiers, tokens, or other authentication material
  • Policy enforcement requiring centralized authorization middleware for sensitive resource operations
  • Audit monitoring for unexpected password changes, cross-tenant requests, and repeated failed or unusual API access

Sources

SourceLink
codeant.aicodeant.ai/security-research/cve-2026-71505-dolibarr-bola-enables-portal-account-takeover
github.comgithub.com/Dolibarr/dolibarr/commit/4cf305ebb958eeffa921aad7c94de179b764f7e7
github.comgithub.com/Dolibarr/dolibarr/releases/tag/24.0.0
vulncheck.comvulncheck.com/advisories/dolibarr-rest-api-broken-object-level-authorization-via-third-party-write-route

Frequently asked

questions

An attacker generally needs an authenticated Dolibarr account with permission to create or modify third-party-related records. The precise scope depends on deployment permissions and API exposure.

No. The issue concerns insufficient authorization on a write operation that may allow a victim company's WebPortal password to be replaced.

Enforce server-side object-level authorization before every sensitive read or write, bind the target company to the user's permitted scope, and omit password verifiers from responses.

Use centralized authorization policies, test cross-tenant and cross-object access in API security tests, apply least-privilege permissions, and review all credential-management endpoints for consistent access checks.

Find out what's already
exploitable in your codebase.