Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAuthenticate as MCP client
-
ExploitInvoke execute_method tool
-
ExecutionCall read/search_read naming denied fields
-
ImpactReceive unredacted restricted data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Requires the Odoo MCP server (erpipe-org/mcp-odoo, versions 1.0.0 through 1.3.2) to expose the execute_method tool and the attacker to hold a valid MCP client session with at least low privileges (PR:L) - not anonymous access. The concrete prerequisite is the ability to call execute_method and reach Odoo's read or search_read ORM methods directly, bypassing the field-level ACL enforcement that the higher-level tools apply; the attacker must also know or guess the names of the restricted fields to request. Limiting factors: exploitation is confined to disclosure of field values the caller could enumerate, grants no integrity or availability impact, and depends on the MCP server being deployed with execute_method available. The prompt-injection path additionally requires an LLM agent with tool-calling access that can be manipulated via untrusted input. |
| Impact | This is a moderate-priority, confidentiality-only issue rather than an urgent emergency. The provided CVSS 4.0 vector (AV:N/AC:L/AT:N/PR:L/UI:N) scores 5.3 (MEDIUM) and indicates a network-reachable, low-complexity attack that still requires some privilege (PR:L) - i.e. an already-authenticated MCP client session, not a fully anonymous attacker. Impact is bounded: VC:L with VI:N/VA:N means limited confidentiality loss and no integrity or availability effect, consistent with CWE-200 field-level information disclosure. No EPSS score was supplied, so exploitation probability cannot be quantified from the data. The CVE is NOT in CISA KEV, so there is no confirmed active exploitation. No separate POC/exploit-code flag was provided; the referenced VulnCheck/hackmd advisory and the GitHub source-line pointer describe the technique but do not constitute a weaponized public exploit. One elevating factor to weigh against the modest CVSS: the description explicitly includes prompt-injected agents as a threat actor, which is realistic for AI/MCP deployments where an LLM can be coerced into calling execute_method - in those environments the effective PR barrier may be weaker than the vector implies. Net: real but contained risk, worth prioritizing for anyone running the affected MCP server in an agentic context, lower priority otherwise given its niche footprint. |
| Exploit ScenarioDerived | An authenticated MCP client - or an AI agent that has been prompt-injected - connected to the Odoo MCP server invokes the execute_method tool to call read or search_read directly, naming fields that the server's field-level ACL would normally redact, and receives those denied values unredacted. No weaponized public exploit is identified at time of analysis, though the VulnCheck advisory and hackmd write-up document the technique in detail. The low attack complexity (AC:L) means no special timing or race conditions are needed once a session exists. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 11, 2026
Field-level access control bypass in Odoo MCP (erpipe-org/mcp-odoo) versions 1.0.0 through 1.3.2 allows an attacker holding a valid, low-privileged MCP client session to read restricted Odoo field values by invoking the execute_method tool and calling the read or search_read ORM methods directly against named denied fields. Exploitation is confidentiality-only, with no integrity or availability impact, and requires authenticated access - the execute_method tool must be exposed and the caller must know or guess the restricted field names; a prompt-injected LLM agent with tool-calling access is an additional attack path. No public exploit code was identified at time of analysis, and the CVSS 4.0 base score of 5.3 reflects a moderate-priority disclosure rather than an emergency, consistent with EPSS-style low-to-moderate risk and no confirmed active exploitation.
RemediationAI
No vendor-released patch or fixed version was identified at time of analysis; versions 1.0.0 through 1.3.2 remain affected, and administrators should track https://github.com/erpipe-org/mcp-odoo and the advisory at https://www.vulncheck.com/advisories/odoo-mcp-1.0.0-through-1.3.2-information-disclosure-via-execute-method-tool for an updated release, then upgrade past 1.3.2 once available. Until then, the highest-value control is to remove or disable the execute_method tool from the MCP server's exposed tool set, or filter it out at the MCP gateway - this closes the bypass path directly, with the trade-off that any agent workflow relying on raw ORM method invocation will break and must be reworked to use the safer, ACL-enforcing tools. Restrict MCP server reachability to trusted networks and trusted client identities (the exploit requires an authenticated, at-least-low-privileged MCP session), and avoid granting MCP sessions broader Odoo record access than they need, since the bypass only reveals fields the underlying Odoo account can reach. Because prompt injection extends the attack surface, sanitize untrusted content passed to tool-calling LLM agents and constrain which tools those agents may invoke; also enable Odoo and MCP-side audit logging of execute_method calls and alert on read/search_read invocations naming sensitive fields such as salary or personal data, recognizing that logging is detective rather than preventive and will not stop disclosure on its own.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Odoo MCP is a Model Context Protocol server (erpipe-org/mcp-odoo) that bridges LLM agents and Odoo ERP instances, exposing tools the agent can call to query business data. The higher-level MCP tools are intended to honor Odoo's field-level ACLs, but the execute_method tool (implemented in src/odoo_mcp/tools_write.py, roughly lines 709-806 at tag v1.3.2) permits clients to invoke arbitrary Odoo ORM methods such as read and search_read. Because execute_method reaches the ORM directly, it sidesteps the wrapper's field-level filtering, so a caller can name fields that the normal tool path would redact and receive their values unredacted. The root cause is classified as CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), a missing-authorization/filtering gap rather than a memory-safety defect. The MCP attack surface also enables a secondary vector: untrusted input consumed by an LLM agent can prompt-inject the agent into making the same execute_method call with attacker-chosen field names, effectively turning a legitimate agent session into the disclosure mechanism.
Know when Odoo Mcp gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N
Network-reachable MCP tool call requiring an authenticated low-privilege session (PR:L), no user interaction, yielding only limited field-level confidentiality loss (C:L) with no integrity or availability impact.
Primary rating from Vendor (VulnCheck).
CVSS VectorVendor: VulnCheck
DescriptionCVE.org
Odoo MCP 1.0.0 through 1.3.2 contains an information disclosure vulnerability that allows MCP clients to bypass the field-level ACL by invoking the execute_method tool. Attackers or prompt-injected agents can call read or search_read through execute_method naming denied fields to receive their values unredacted.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
EUVD-2026-97012
GHSA-hmxx-h27g-fgrq
NVD
CVE.org
EPSS
Exploit-DB