CVE-2021-44460

Improper access control in Odoo Community 13.0 and earlier and Odoo Enterprise 13.0 and earlier allows users with deactivated accounts to access the system with the deactivated account and any permission it still holds, via crafted RPC requests.

Published: 2023-04-25 Last update: 2026-06-17 Assigner: [email protected] Source: [email protected]

Conclusion & alert: CVE-2021-44460 is rated Moderate Risk (42.8/100): CVSS Medium severity, with low exploitation likelihood (EPSS 0.69%). Mandatory action: Review affected assets and schedule remediation.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Exploit prediction scoring system (EPSS) score for CVE-2021-44460

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2026-06-15 0.59% 0.69% +0.09%
2 2026-05-13 0.47% 0.59% +0.13%
3 2026-03-17 0.47%

Full EPSS history (13 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2021-44460

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
6.5 3.1 MEDIUM
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:N)
Data isn’t meaningfully altered or forged.
Availability (A:N)
Service keeps running; no real outage angle.
2.8 3.6 [email protected]
7.4 3.0 HIGH
CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:H)
Even with access, the exploit needs extra luck, timing, or a fussy environment to actually work.
Privileges required (PR:N)
No account or special rights needed—anonymous or random user is enough.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:N)
Service keeps running; no real outage angle.
2.2 5.2 [email protected]

Weakness enumeration for CVE-2021-44460

OS Trackers for CVE-2021-44460

vendor priority summary link
debian unimportant CVE-2021-44460 unimportant priority: Debian including 1 source packages (odoo), 2 status rows across 2 suites (bullseye, sid): resolved 2. https://security-tracker.debian.org/tracker/CVE-2021-44460
ubuntu medium CVE-2021-44460 medium priority: Ubuntu including 1 source packages (odoo), 13 status rows across 13 suites (bionic, focal, jammy, kinetic, lunar, mantic, noble, oracular, plucky, questing, trusty, upstream, xenial): ignored 7, needs-triage 3, DNE 2, not-affected 1. https://ubuntu.com/security/CVE-2021-44460

Affected software / configurations for CVE-2021-44460

Vendor Product Version Raw CPE
odoo odoo <= 13.0 cpe:2.3:a:odoo:odoo:*:*:*:*:community:*:*:*
odoo odoo <= 13.0 cpe:2.3:a:odoo:odoo:*:*:*:*:enterprise:*:*:*

References for CVE-2021-44460

URL Tags
https://github.com/odoo/odoo/issues/107685 Issue Tracking Patch Vendor Advisory
cvelogic Threat Intelligence