dbcve.org
OdooApplication

CVE-2019-11784

MEDIUM · 6.5 CVSS v3.1 Published 2020-12-22
Fix available
A fix is available. Upgrade to after 14.0 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Improper access control in mail module (notifications) in Odoo Community 14.0 and earlier and Odoo Enterprise 14.0 and earlier, allows remote authenticated users to obtain access to arbitrary messages in conversations they were not a party to.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The mail module in Odoo 14.0 and earlier contains an improper access control vulnerability where the system fails to properly validate user permissions when accessing notification messages. Authenticated users can directly reference message IDs in conversations they were not invited to, allowing them to read arbitrary messages they should not have access to.

MitigationApply the vendor patch or upgrade to a patched version of Odoo that includes proper access control enforcement for mail notifications. Review existing access control rules in the mail module to ensure all message access paths are properly authorized.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OdooApplication
Affected:<= 14.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Odoo version
    In Odoo, go to Apps > Apps, or check the __manifest__.py / __init__.py files in the Odoo installation directory. Look for the version declaration (typically 'version' field in manifest or in the Odoo about section).
    Affected if The installed version is 14.0 or any earlier version (e.g., 13.0, 12.0, etc.)
  2. Verify the mail module is installed and active
    Navigate to Apps > Apps in the Odoo interface and search for 'mail' or 'incoming mail'. Check if the 'Mail' module (internal name: mail) shows as installed. Alternatively, check the ir_module_module table in the database for module name 'mail' with state 'installed'.
    Affected if The mail module is installed and in use (required for this vulnerability to apply)
  3. Inspect mail.message access control rules
    Query the ir.model.access model (access control list) for mail.message records: SELECT * FROM ir_model_access WHERE model_id = (SELECT id FROM ir_model WHERE model = 'mail.message'); Or view via Settings > Technical > Security > Access Controls, filter for 'mail.message'.
    Affected if There are access control rules present but they do not properly restrict message read access based on thread membership, or no rule explicitly enforces conversation invitation validation
  4. Review custom mail module extensions
    Check for custom modules that modify mail.message access rights: look in /addons/ or custom module directories for models inheriting mail.message or overriding access methods (check for 'mail.thread' inheritance and _check_access methods). Inspect any installed custom modules that extend the mail functionality.
    Affected if Custom code modifies or bypasses standard mail.message access controls, or implements its own message access logic without proper permission checks

You are affected if you run Odoo version 14.0 or earlier and have the mail module installed, with access control rules that do not enforce strict conversation membership validation for notification message reads.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 14.0
Interim mitigation

Apply the vendor patch or upgrade to a patched version of Odoo that includes proper access control enforcement for mail notifications. Review existing access control rules in the mail module to ensure all message access paths are properly authorized.

Fix this in Odoo Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,120.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-11784 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-11784 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data