CVE-2019-11782
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 Odoo Community 14.0 and earlier and Odoo Enterprise 14.0 and earlier, allows remote authenticated users with access to contact management to modify user accounts, leading to privilege escalation.
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 · moderate confidenceOdoo versions 14.0 and earlier contain an improper access control vulnerability where authenticated users with contact management permissions can modify arbitrary user accounts, enabling privilege escalation to administrative levels. The contact management interface lacks proper authorization checks before allowing user account modifications.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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.
-
Identify Odoo installation and versionAccess Odoo system information through the web UI (Settings > About) or check the Odoo configuration files (odoo.conf) or the database for the ir_module_module table to determine the installed version numberAffected if The Odoo version is 14.0 or any earlier version (e.g., 13.0, 12.0, etc.)
-
Verify contact management module is installedNavigate to Apps menu in Odoo and search for 'Contacts' or 'Contact Management' module, or query the ir_module_module table for modules with 'contact' in the name that are installedAffected if The Contacts or Contact Management module is installed and enabled in the Odoo instance
-
Check for users with contact management permissionsNavigate to Settings > Users > Users or Groups, and review which users are assigned to the Contact Manager group or have contact management-related access rightsAffected if Any user accounts are assigned to roles with contact management or contact creation/modification permissions
-
Confirm contact records include user account referencesIn the Contacts application, inspect contact records to see if any contacts are linked to internal user accounts (as opposed to external partners), or check the res.partner table for records where user_id field is populatedAffected if Contacts exist that are linked to internal Odoo user accounts, allowing the contact interface to potentially modify user records
-
Test for unauthorized access via contact interfaceLog in as a user with only contact management permissions (non-admin), navigate to Contacts, open a contact linked to an internal user account, and attempt to modify user-related fields such as groups or access rightsAffected if A user with only contact management permissions can successfully modify fields on contact records that belong to administrative or other privileged user accounts
You are affected if running Odoo version 14.0 or earlier, the Contacts module is installed, and users with only contact management permissions can modify contact records that are linked to privileged user accounts.
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 proper access control checks in the contact management module to verify that users attempting to modify user accounts have appropriate permissions. Restrict contact management functionality from accessing or modifying user account records, and apply the principle of least privilege to contact management roles.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-11782 — 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-11782 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