CVE Intelligence
Skip to main content
HIGH

CVE-2021-23186

CVE-2021-23186 Vulnerability Analysis & Exploit Intelligence

A sandboxing issue in Odoo Community 15.0 and earlier and Odoo Enterprise 15.0 and earlier allows authenticated administrators to access and modify database contents of other tenants, in a multi-tenant system.

Published Updated Sources: cvelistV5, odoo

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Unreported

no source claims exploitation

EPSS

1%

chance of exploitation in 30 days

Affects

odoo

2 products listed

CVSS base

8.7

HIGH

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

None

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Affected scope

The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.

Vendors (1)

odoo

Products (2)

odoo communityodoo enterprise

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
8.7CVSS 3.0HIGH——cvelistV5

Weakness & attack patterns

  • CWE-267

Attack patterns reported against this CVE. The ATT&CK techniques below are inferred from its weakness class.

  • T1123Audio Capture
  • T1125Video Capture
  • T1115Clipboard Data

References

2 on the record

Elsewhere on this site

  • odooevery CVE for this vendor
  • CWE-267other pages naming this weakness

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.