CVE-2019-11783
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 · uneditedImproper access control in mail module (channel partners) in Odoo Community 14.0 and earlier and Odoo Enterprise 14.0 and earlier, allows remote authenticated users to subscribe to arbitrary mail channels uninvited.
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 confidenceOdoo fails to enforce proper authorization checks when users attempt to subscribe to mail channels. Authenticated users can subscribe to any channel without invitation by manipulating the subscription request, bypassing the intended access control that should require an invitation or appropriate permissions.
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<= 14.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Odoo versionAccess Odoo via UI (About Odoo in Settings) or check the odoo-bin --version output, or inspect the odoo/release.py file for the version numberAffected if The installed version is 14.0 or earlier (any version listed as 14.0, 13.0, 12.0, etc.)
-
Verify mail channel module is activeNavigate to Apps menu in Odoo and search for 'Mail' or 'Discuss' module, or check the 'discuss' addon is present in the addons pathAffected if The mail/discuss channel module is installed and in use on the instance
-
Check channel subscription access rightsReview the discuss.channel model access rights in Odoo: go to Settings > Technical > Security > Access Rights, or inspect ir.model.access records for 'discuss.channel'Affected if The access rights allow authenticated users (without specific channel invitation) to create or write to discuss.channel subscription records, or no invitation-based validation is enforced
-
Inspect subscription request handlingReview the controller or model method handling channel subscription (typically in addons/discuss/controllers or addons/mail/models), look for code that processes subscription requestsAffected if The subscription logic lacks server-side validation to check for valid invitation or proper channel permissions before allowing subscription
The environment is affected if running Odoo version 14.0 or earlier with the mail/discuss module active, where the channel subscription feature lacks proper invitation-based authorization checks.
Generated from the published advisory. Verify against your own configuration.
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 dataImplement server-side validation to verify that the requesting user has proper permissions or an existing invitation before allowing channel subscription. Restrict channel subscription to invited users only.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11783 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-11783 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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