Skip to content

Dolibarr

Bug bounty on Sorona dolibarr.org

Accepting reports open-source
Top reward
$1,500
Top severity paid
Critical
Assets in scope
13
Public CVEs
60
Last change
No changes yet

At a glance

What to know before you start testing.

Pays from $1,500
for critical bugs.
Partial safe harbor
Some legal protection; read the terms.
Publish after a fix
Coordinate the timing with the company.

Rewards

What Sorona lists as the payout for each severity.

Severity Reward
Critical $1,500+
High $700+
Medium $300+
Low $100 $100 / 1 month Claude Max
Safe harbor
Partial Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf.

Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original

Scope

13 assets you may test, 6 excluded.

Web 1

  • https://www.dolibarr.org

Products and areas 12

  • Email sending and the mass-mailing module, including any template a user supplies
  • External authentication connectors, including LDAP and any single sign-on module in the core tree
  • List views, search filters and the SQL those parameters are built into
  • The core modules a real deployment turns on: third parties and contacts, proposals, orders, invoices, accounting, stock, projects, HR and expense reports
  • The document generation layer, which renders ODT and PDF output from templates that an administrator can edit
  • The electronic content management module and every upload and download route that touches the documents directory
  • The installer and the upgrade path, plus the module activation mechanism that enables new code on a running instance
  • The multicompany arrangement, where one installation serves several legal entities out of one database
  • The permission system, which grants rights per module per user and is the single control standing between a limited employee and the company's finances
  • The policy takes private reports on any supported version, defining support as the five most recent major releases, and states eligibility rules rather than a component carve-out. Everything shipped in the core tree inside that window is in scope
  • The public-facing interfaces Dolibarr exposes to unauthenticated visitors, including public ticket submission, online payment pages and online signature links
  • The REST API and the API key mechanism scripted consumers authenticate with
Out of scope (6)
  • A permission grant an administrator made deliberately, since the module permission matrix is a configuration decision
  • Hosting and server configuration, including a web root that exposes the documents directory
  • Modules from Dolistore and other external module authors, which ship outside the core repository
  • Releases older than the five most recent majors, the support window the policy defines
  • Scanner output submitted without a working reproduction against a supported release
  • Upstream PHP library issues, unless Dolibarr's own use of the library is what makes the defect reachable

Rules

What the policy asks of you, and the bug types it won't reward, quoted from Sorona's policy.

While testing

  • Submit through sorona.xyz.
  • Prefer a GitHub private security advisory on Dolibarr/dolibarr, the channel the policy recommends first.
  • The policy defines support as the five most recent major versions. A finding against anything older falls outside it
  • The policy asks security testers to append -securitytest-for-dolibarr to their User-Agent string
  • Say which modules were enabled.
  • Hold the detail until the fixed releases are out across that window

Not accepted

  • A permission grant an administrator made deliberately
  • Upstream PHP library issues, unless Dolibarr's own use of the library is what makes the defect reachable
  • Hosting and server configuration, including a web root that exposes the documents directory
  • Scanner output submitted without a working reproduction against a supported release

Summarised with AI from the program policy on Sorona, read 12 Nov 2026, and checked word for word against it. Read the original

Changes

Tracked since 11 Nov 2026. Last checked 1 hour ago.

No changes yet. When the rewards or scope move, you will see it here and in the RSS feed.

Public CVEs

Published vulnerabilities in this vendor's products, from the NVD.

Search NVD
CVESeverityPublished
CVE-2026-81728 High 8.6 27 Aug 2026
CVE-2026-81729 High 7.1 27 Aug 2026
CVE-2026-81730 High 8.8 27 Aug 2026
CVE-2026-77923 Medium 5.3 24 Aug 2026
CVE-2018-25357 Critical 9.3 23 May 2026
CVE-2025-67486 High 8.6 8 May 2026
CVE-2026-31019 High 8.8 21 Apr 2026
CVE-2026-31018 High 8.8 21 Apr 2026
CVE-2026-23500 Critical 9.4 17 Apr 2026
CVE-2019-25710 High 8.8 12 Apr 2026
CVE-2026-22666 High 8.6 7 Apr 2026
CVE-2026-34036 Medium 6.5 31 Mar 2026
CVE-2019-25450 High 7.1 22 Feb 2026
CVE-2019-25452 High 8.8 22 Feb 2026
CVE-2021-47779 High 8.4 16 Jan 2026
CVE-2025-56588 High 8.8 1 Oct 2025
CVE-2024-55227 Critical 9.0 27 Jan 2025
CVE-2024-55228 Critical 9.0 27 Jan 2025
CVE-2021-3991 Medium 4.3 15 Nov 2024
CVE-2024-37821 High 8.8 18 Jun 2024
CVE-2024-5314 Critical 9.1 24 May 2024
CVE-2024-5315 Critical 9.1 24 May 2024
CVE-2024-31503 High 7.5 17 Apr 2024
CVE-2024-29477 High 8.8 3 Apr 2024
CVE-2024-23817 High 7.1 25 Jan 2024
CVE-2023-4198 Medium 6.5 1 Nov 2023
CVE-2023-4197 High 7.5 1 Nov 2023
CVE-2023-5842 Medium 4.8 30 Oct 2023
CVE-2023-5323 Medium 6.1 1 Oct 2023
CVE-2023-38888 Critical 9.6 20 Sep 2023
CVE-2023-38886 High 7.2 20 Sep 2023
CVE-2023-38887 High 8.8 20 Sep 2023
CVE-2023-33568 High 7.5 13 Jun 2023
CVE-2023-30253 High 8.8 29 May 2023
CVE-2022-4093 Critical 9.8 21 Nov 2022
CVE-2022-43138 Critical 9.8 17 Nov 2022
CVE-2022-40871 Critical 9.8 12 Oct 2022
CVE-2022-2060 Medium 5.4 13 Jun 2022
CVE-2022-30875 Medium 6.1 8 Jun 2022
CVE-2021-37517 High 7.5 31 Mar 2022
CVE-2021-36625 High 8.8 31 Mar 2022
CVE-2022-0819 High 8.8 2 Mar 2022
CVE-2022-0746 Medium 4.3 25 Feb 2022
CVE-2022-0731 Medium 6.5 23 Feb 2022
CVE-2022-0414 Medium 4.3 31 Jan 2022
CVE-2022-0224 Critical 9.8 14 Jan 2022
CVE-2022-0174 Medium 4.3 10 Jan 2022
CVE-2022-22293 Medium 5.4 2 Jan 2022
CVE-2021-42220 Medium 5.4 15 Dec 2021
CVE-2021-33618 Medium 6.1 10 Nov 2021
CVE-2021-33816 Critical 9.8 10 Nov 2021
CVE-2021-25956 Medium 4.7 17 Aug 2021
CVE-2021-25957 High 8.8 17 Aug 2021
CVE-2021-25955 Critical 9.0 15 Aug 2021
CVE-2021-25954 Medium 4.3 9 Aug 2021
CVE-2020-35136 High 7.2 23 Dec 2020
CVE-2020-14209 High 8.8 2 Sep 2020
CVE-2020-13828 Medium 5.4 31 Aug 2020
CVE-2020-14201 Medium 6.5 21 Aug 2020
CVE-2020-14475 Medium 6.1 19 Jun 2020

Original policy

Copied from sorona.xyz on 12 Nov 2026. The summaries on this page are made from it; the live page may have changed since.

Skip to content What this pays This project runs no bounty of its own. sorona.xyz pays you directly on qualified, reproduced findings. Severity │ sorona.xyz pays Critical │ $1,500+ High │ $700+ Medium │ $300+ Low │ $100 / 1 month Claude Max Submit a vulnerability CVE history 2 Last 12 months 4 Lifetime Access control 35 % Injection 25 % XSS/CSRF 22 % File handling 18 % Latest advisories Loading the feed Overview Dolibarr is a volunteer-built ERP and CRM with a very large install base across European small businesses, associations and municipalities, carrying invoicing, accounting and payroll data for organisations that have no security team at all. Its published advisory count is a poor guide to the real rate. The project holds no CNA, does not issue CVEs itself and pushes advisories over its own feed, so the GitHub figure understates what has actually been fixed. Dolibarr ran a paid programme on Yogosha and closed it at the end of 2024, and the association states plainly that it has no funds for bounties. sorona.xyz pays you directly on qualified, reproduced findings. In scope The policy takes private reports on any supported version, defining support as the five most recent major releases, and states eligibility rules rather than a component carve-out. Everything shipped in the core tree inside that window is in scope The permission system, which grants rights per module per user and is the single control standing between a limited employee and the company's finances The core modules a real deployment turns on: third parties and contacts, proposals, orders, invoices, accounting, stock, projects, HR and expense reports The public-facing interfaces Dolibarr exposes to unauthenticated visitors, including public ticket submission, online payment pages and online signature links The REST API and the API key mechanism scripted consumers authenticate with The document generation layer, which renders ODT and PDF output from templates that an administrator can edit The electronic content management module and every upload and download route that touches the documents directory The multicompany arrangement, where one installation serves several legal entities out of one database External authentication connectors, including LDAP and any single sign-on module in the core tree The installer and the upgrade path, plus the module activation mechanism that enables new code on a running instance List views, search filters and the SQL those parameters are built into Email sending and the mass-mailing module, including any template a user supplies Out of scope Modules from Dolistore and other external module authors, which ship outside the core repository Releases older than the five most recent majors, the support window the policy defines A permission grant an administrator made deliberately, since the module permission matrix is a configuration decision Upstream PHP library issues, unless Dolibarr's own use of the library is what makes the defect reachable Hosting and server configuration, including a web root that exposes the documents directory Scanner output submitted without a working reproduction against a supported release Most-valued findings Permission-matrix bypass, where a user without the right for a module reaches its data or its actions anyway. This is the highest-value class in a product whose entire authorisation model is that matrix Anything reachable from the unauthenticated public interfaces: the public ticket form, the online payment page and the signature links, since those are the parts of Dolibarr exposed to the open internet on purpose SQL injection through list filters, search parameters or sort arguments, which in this codebase are assembled into queries across a very large number of module screens Path traversal and unauthorised retrieval in the document module, where invoices, payslips and contracts sit as files on disk File upload handling that lands an executable file somewhere the web server will run it Cross-entity access on a multicompany installation, where one legal entity's accounting reaches another's Template injection in the ODT or PDF generation path, where an administrator-editable template becomes code execution Authentication and session defects, including the LDAP connector and password reset Stored cross-site scripting in a third-party record, an invoice note or a ticket message that later renders in an administrator's session Program rules Submit through sorona.xyz. This project runs no bounty of its own; we validate, coordinate disclosure with the maintainers, and pay you directly. Prefer a GitHub private security advisory on Dolibarr/dolibarr, the channel the policy recommends first. [email protected] is the documented alternative The old Yogosha programme link is still sitting in the SECURITY.md source inside an HTML comment. It closed at the end of 2024, it is invisible in the rendered page, and following it wastes your time The policy defines support as the five most recent major versions. A finding against anything older falls outside it The policy asks security testers to append -securitytest-for-dolibarr to their User-Agent string so the project can tell research traffic from a live attack. Do it Say which modules were enabled. Dolibarr is heavily modular and most of the product is optional, so a reproduction depends on the module set as much as on the version Advisories go out on the project's own feed at cti.dolibarr.org rather than as CVEs, so expect credit there rather than in the CVE database Disclosure Coordinated privately with a volunteer maintainer group through GitHub private advisories or the security address, then published on the project's own security feed. Dolibarr holds no CNA and does not assign CVE identifiers itself, so a finding may never receive one unless a third party steps in. The five-major-version support window decides which branches get a backport. Hold the detail until the fixed releases are out across that window, since the install base runs several majors behind at any moment. Safe harbor Sorona will not pursue legal action against you for good-faith research submitted to us in line with this policy. We cannot speak for the upstream project, its vendor, or any third party, and we do not grant authorization on their behalf. You are responsible for understanding and following the laws that apply to you, wherever you are, and for staying within any scope the project has defined. Submit a vulnerability