Skip to content

Odoo Community

By Odoo SA Bug bounty on Sorona odoo.com

Accepting reports open-source
Top reward
$1,500
Top severity paid
Critical
Assets in scope
16
Public CVEs
54
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.
Hall of fame
Yes Acknowledgement is a Hall of Fame entry, which the policy reserves for confirmed critical findings.

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

Scope

16 assets you may test, 6 excluded.

Web 1

  • https://www.odoo.com

Products and areas 15

  • Attachments and the filestore, both the write path and the access check on retrieval
  • Authentication modules in the Community tree, including LDAP and OAuth, plus API key handling and session management
  • Mail, mass mailing and the inbound mail gateway, which processes messages from unauthenticated senders
  • Multi-company record rules, where one database serves several legal entities and the separation between them is enforced in rules rather than in schema
  • Payment provider modules and the callback or webhook route a gateway uses to report a completed transaction
  • Point of sale, including its offline mode and the session data held on a client until it syncs
  • The accounting and invoicing modules, including bank synchronisation and the payment reconciliation flow
  • The database manager and the master password that protects database creation, duplication and backup
  • The module installation and update mechanism, which loads new Python and XML into a running instance
  • The ORM and its access-rights layer: model access rules, record rules and the field-level restrictions every module relies on for authorisation
  • The portal, where an external user signs in to view their own quotations, invoices and tickets
  • The published programme asks for any security issue in Odoo by email to [email protected], and the signed security.txt gives the same address for the whole product. No component carve-out is stated, so the Community source tree is in scope as a whole
  • The QWeb template engine, used for reports, website pages and email, the main server-side template evaluation surface
  • The web controller and RPC surface, covering the JSON-RPC and XML-RPC entry points that expose model methods to any authenticated caller
  • The website builder and eCommerce modules, plus every public controller they expose to unauthenticated visitors
Out of scope (6)
  • Access rights or record rules an administrator configured deliberately
  • Deployment configuration, including an instance that leaves the database manager reachable in production
  • Enterprise-only modules, which are not published in the Community tree this entry covers
  • Odoo SA's own hosting and commercial SaaS infrastructure, which is the vendor's estate rather than the Community codebase
  • Third-party modules from the Odoo Apps store and from community collections such as the OCA repositories
  • Upstream Python dependency issues, unless Odoo's own use of the dependency 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.
  • Email the address on the policy page , the private address published on Odoo's security-report page and corroborated by its signed security.txt
  • Encrypt sensitive detail to the key published in the security.txt at download.odoo.com
  • Say which edition and which major version you tested.
  • Name the modules that were installed.

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-2024-36259 High 7.5 25 Feb 2025
CVE-2024-12368 High 8.1 25 Feb 2025
CVE-2023-48050 Critical 9.8 15 Dec 2023
CVE-2021-26947 Medium 6.1 25 Apr 2023
CVE-2021-44460 Medium 6.5 25 Apr 2023
CVE-2021-44461 Medium 6.1 25 Apr 2023
CVE-2021-44465 Medium 4.3 25 Apr 2023
CVE-2021-44476 Medium 6.8 25 Apr 2023
CVE-2021-44547 Critical 9.1 25 Apr 2023
CVE-2021-44775 Medium 6.1 25 Apr 2023
CVE-2021-45071 Medium 6.1 25 Apr 2023
CVE-2021-45111 High 8.1 25 Apr 2023
CVE-2021-23166 High 8.7 25 Apr 2023
CVE-2021-23176 Medium 6.5 25 Apr 2023
CVE-2021-23178 High 7.5 25 Apr 2023
CVE-2021-23186 High 8.7 25 Apr 2023
CVE-2021-23203 High 7.5 25 Apr 2023
CVE-2021-26263 Medium 6.1 25 Apr 2023
CVE-2020-29396 High 8.8 22 Dec 2020
CVE-2018-15633 Medium 6.1 22 Dec 2020
CVE-2018-15634 Medium 6.1 22 Dec 2020
CVE-2018-15638 Medium 5.4 22 Dec 2020
CVE-2018-15641 Medium 5.4 22 Dec 2020
CVE-2018-15645 Medium 6.5 22 Dec 2020
CVE-2019-11781 High 8.8 22 Dec 2020
CVE-2019-11782 Medium 6.5 22 Dec 2020
CVE-2019-11783 Medium 6.5 22 Dec 2020
CVE-2019-11784 Medium 6.5 22 Dec 2020
CVE-2019-11785 Medium 4.3 22 Dec 2020
CVE-2019-11786 Medium 4.3 22 Dec 2020
CVE-2018-15632 Critical 9.1 22 Dec 2020
CVE-2019-11780 High 8.1 19 Dec 2019
CVE-2018-14733 High 7.5 5 Jul 2019
CVE-2018-14859 High 8.1 3 Jul 2019
CVE-2018-14860 Critical 9.1 3 Jul 2019
CVE-2018-14865 Medium 6.5 3 Jul 2019
CVE-2018-14861 Medium 6.5 3 Jul 2019
CVE-2018-14862 Medium 6.5 3 Jul 2019
CVE-2018-14863 High 8.1 3 Jul 2019
CVE-2018-14864 Medium 6.5 3 Jul 2019
CVE-2018-14866 Medium 4.3 3 Jul 2019
CVE-2018-14885 Critical 9.8 28 Jun 2019
CVE-2018-14886 Medium 4.9 28 Jun 2019
CVE-2018-14887 Medium 6.5 28 Jun 2019
CVE-2018-14867 Medium 5.3 28 Jun 2019
CVE-2018-14868 Medium 6.5 28 Jun 2019
CVE-2017-5871 Medium 5.4 22 May 2019
CVE-2018-15631 Medium 6.5 9 Apr 2019
CVE-2018-15635 Medium 5.9 9 Apr 2019
CVE-2018-15640 High 8.8 9 Apr 2019
CVE-2017-10803 Medium 6.5 4 Jul 2017
CVE-2017-10804 Critical 9.8 4 Jul 2017
CVE-2017-10805 High 8.8 4 Jul 2017
CVE-2017-9416 Medium 6.5 4 Jun 2017

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 Latest advisories Loading the feed Overview Odoo is the largest open-source ERP by deployment, running accounting, inventory, payroll, point of sale and payment flows for an enormous long tail of companies, and the Community edition is the free half of a product a multi-billion-euro vendor sells. The reference point for cost is what a single tenant holds: invoices, salary records and payment provider configuration, all behind one login on one database. Odoo SA runs a mature disclosure programme with a PGP-signed security.txt and a published acknowledgements page, and the reward for a confirmed critical finding is a line in the Security Hall of Fame. sorona.xyz pays you directly on qualified, reproduced findings. In scope The published programme asks for any security issue in Odoo by email to [email protected] , and the signed security.txt gives the same address for the whole product. No component carve-out is stated, so the Community source tree is in scope as a whole The ORM and its access-rights layer: model access rules, record rules and the field-level restrictions every module relies on for authorisation The web controller and RPC surface, covering the JSON-RPC and XML-RPC entry points that expose model methods to any authenticated caller Multi-company record rules, where one database serves several legal entities and the separation between them is enforced in rules rather than in schema The accounting and invoicing modules, including bank synchronisation and the payment reconciliation flow Point of sale, including its offline mode and the session data held on a client until it syncs The website builder and eCommerce modules, plus every public controller they expose to unauthenticated visitors The portal, where an external user signs in to view their own quotations, invoices and tickets Payment provider modules and the callback or webhook route a gateway uses to report a completed transaction The QWeb template engine, used for reports, website pages and email, the main server-side template evaluation surface Attachments and the filestore, both the write path and the access check on retrieval The module installation and update mechanism, which loads new Python and XML into a running instance The database manager and the master password that protects database creation, duplication and backup Authentication modules in the Community tree, including LDAP and OAuth, plus API key handling and session management Mail, mass mailing and the inbound mail gateway, which processes messages from unauthenticated senders Out of scope Enterprise-only modules, which are not published in the Community tree this entry covers Third-party modules from the Odoo Apps store and from community collections such as the OCA repositories Odoo SA's own hosting and commercial SaaS infrastructure, which is the vendor's estate rather than the Community codebase Access rights or record rules an administrator configured deliberately Upstream Python dependency issues, unless Odoo's own use of the dependency is what makes the defect reachable Deployment configuration, including an instance that leaves the database manager reachable in production Most-valued findings Access-rights and record-rule bypass in the ORM. Every module in the product delegates authorisation there, so one gap is a gap across the whole ERP at once Multi-company separation failures, where one legal entity's accounting, payroll or customer data becomes readable from another entity on the same database RPC methods callable without the group or record rule they assume. The RPC surface exposes model methods broadly and the checks are applied by convention rather than uniformly Anything unauthenticated reachable through the website, eCommerce or portal controllers, since that is the part of Odoo deliberately facing the open internet Payment provider callback forgery that marks an order or invoice paid without a genuine transaction QWeb template injection in a report, a website page or a mail template, where an editable template reaches server-side execution The database manager and master password path, which reaches database creation, duplication and backup download on a production host Attachment and filestore access control, since on this product the files behind it are contracts, invoices and payslips Point-of-sale session and offline sync handling, where transaction data leaves the server and returns The inbound mail gateway, one of the few paths in Odoo where a complete stranger's input reaches server-side processing without any account 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. Email [email protected] , the private address published on Odoo's security-report page and corroborated by its signed security.txt Encrypt sensitive detail to the key published in the security.txt at download.odoo.com The repository does not use GitHub security advisories and private vulnerability reporting is not enabled on odoo/odoo, so there is no advisory button here Say which edition and which major version you tested. Community and Enterprise share a core, and Enterprise modules are not part of the Community tree Name the modules that were installed. Odoo is modular and the reachable surface changes completely between a bare install and a real deployment, so the module list is part of the reproduction Acknowledgement is a Hall of Fame entry, which the policy reserves for confirmed critical findings. There is no payment to negotiate Disclosure Coordinated privately with Odoo SA's security team by email. The programme is well established, with a signed security.txt, a published encryption key and a public acknowledgements page, so expect a professional process rather than a volunteer inbox. Odoo publishes through its own channel rather than as GitHub advisories, and it maintains several supported majors at once, so the practical embargo runs until fixes land across the supported series and the hosted estate has been rolled forward. 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