Security fix · CVE-2019-11786
[REF] web_tour: prepare to change the default action in tour_compiler Currently, in tour_compiler, to check that an element is actually present in the DOM in a step, t…
Published Dec 22, 2020 · catalog updated Jun 17, 2026 · Odoo Odoo
Check if you run it
No confirmed exploitation is on record for CVE-2019-11786. EPSS is 0.70%. Act only if a listed version of Odoo Odoo is installed.
Gaps on this record
- No version range is stored. A customer cannot check an installed version against this record.
- No vendor fix or required action is stored. Compare the linked advisory before you change production.
- Severity
- Medium4.3
- Known exploitation
- Not in CISA/VulnCheck KEV
- EPSS
- 0.70%
- Remediation
- Fix linked
- Affected products
- cpe odoo/odoo
[REF] web_tour: prepare to change the default action in tour_compiler Currently, in tour_compiler, to check that an element is actually present in the DOM in a step, there are 2 possibilities. - => Checks that the element is in the DOM. The latter can be disabled. - => Checks that the element is in the DOM (because this is what is done by default). However, if the element is disabled, the step will be aborted. In the codebase, we can see a lot of and . However, the behavior is not exactly the same. What's more, there are 2 ways to do "the same thing". In order to clarify the turns API, it was
Are you affected?
Enter the version you run. The result uses only the ranges stored on this record.
The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.
- cpe odoo/odooversion unspecified
How to fix CVE-2019-11786
Recommended remediation
1 related fix commit linked. Confirm the fix covers your edition and version.
Official advisories
What to do
Three questions, each answered from this record only. Confirm the vendor advisory before you patch.
Should you patch?
No confirmed exploitation is on record for CVE-2019-11786. EPSS is 0.70%. Act only if a listed version of Odoo Odoo is installed.
Which versions are affected?
Affected version ranges are not on this record. Compare the installed version with the linked vendor advisory before you change production.
What should an analyst verify?
CWE-284: Improper Access Control. EPSS 0.70%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.
Technology hubs
Code
The project this record applies to. Exploit listings stay in References.
Related records
Linked stories and findings that share CVE identifiers or explicit correlation edges.
Vulnerability · fixes
4cc6ca11801c823443bfe89c0c36d8069c9f9bce
Related Odoo Git fixes
Quoted Community commit messages that cite this CVE. Presence of a commit is not proof that every edition or backport includes the fix. Enterprise proprietary diffs are never shown here. Timeline
Jun 5, 2024 · cited
[REF] web_tour: prepare to change the default action in tour_compiler
[REF] web_tour: prepare to change the default action in tour_compiler Currently, in tour_compiler, to check that an element is actually present in the DOM in a step, there are 2 possibilities. - `isCheck: true` => Checks that the element is in the DOM. The latter can be disabled. - `run() {}` => Checks that the element is in the DOM (because this is what is done by default). However, if the element is disabled, the step will be aborted. In the codebase, we can see a lot of `run() {} //it's a check` and `isCheck:true`. However, the behavior is not exactly the same. What's more, there are 2 ways to do "the same thing". In order to clarify the turns API, it was decided to no longer put an action (step.run) by default. (Previously, the default action was the "click" action). From then on, it is no longer necessary to stipulate `step.isCheck: true` nor `run() {}`. The corollary is that now…
https://github.com/odoo/odoo/commit/4cc6ca11801c823443bfe89c0c36d8069c9f9bce
Timeline
Detection, updates, and resolution for this record.
Dec 22, 2020 · Catalog
Detected
Improper access control in Odoo Community 13.0 and earlier and Odoo Enterprise 13.0 and earlier, allows remote authenticated users to modify translated terms, which may lead to arbitrary content modification on translatable elements.
Jun 16, 2026 · Catalog
Updated
Improper access control in Odoo Community 13.0 and earlier and Odoo Enterprise 13.0 and earlier, allows remote authenticated users to modify translated terms, which may lead to arbitrary content modification on translatable elements.
Jun 17, 2026 · NIST NVD
Updated
Improper access control in Odoo Community 13.0 and earlier and Odoo Enterprise 13.0 and earlier, allows remote authenticated users to modify translated terms, which may lead to arbitrary content modification on translatable elements.
Sources
- CVE.orgVulnerability recordCVE-2019-11786
Official CVE identifier
cve.org - FIRST EPSSExploitation probabilityCVE-2019-11786
30-day exploitation probability 0.7%
first.org - NIST NVDVulnerability recordCVE-2019-11786
Improper access control in Odoo Community 13.0 and earlier and Odoo Enterprise 13.0 and earlier, allows remote authenticated users to modify translated terms, which may lead to arbitrary content modification on translatable elements.
nvd.nist.gov - Odoo SecurityVendor advisoryCVE-2019-11786
Odoo or OpenERP product vulnerability. Vendor discussion stays on the Odoo tracker.
github.com - Odoo Community GitGit security fix referenceCVE-2019-11786
[REF] web_tour: prepare to change the default action in tour_compiler Currently, in tour_compiler, to check that an element is actually present in the DOM in a step, there are 2 possibilities. - => Checks that the element is in the DOM. The latter can be disabled. - => Checks tha
github.com
References
Freshness
Last verified in this catalog Oct 17, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.