CVE-2021-44461
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 · uneditedCross-site scripting (XSS) issue in Accounting app of Odoo Enterprise 13.0 through 15.0, allows remote attackers who are able to control the contents of accounting journal entries to inject arbitrary web script in the browser of a victim.
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 · high confidenceA stored Cross-Site Scripting (XSS) vulnerability exists in the Accounting application of Odoo Enterprise versions 13.0 through 15.0. Attackers who can control the contents of accounting journal entries can inject malicious JavaScript that executes in victims' browsers when they view those entries.
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>= 13.0, <= 15.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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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 versionAccess Odoo and navigate to Apps menu, or check the Odoo about page (usually at /web/about), or inspect the Odoo backend footer which displays the version number. Compare against affected range 13.0 to 15.0.Affected if The installed Odoo version is Enterprise edition within 13.0 through 15.0 inclusive.
-
Confirm Accounting module is installedNavigate to the Apps menu in Odoo and search for 'Accounting' or 'Invoicing'. Verify the module is installed and active in the database.Affected if The Accounting or Invoicing module is installed and enabled in the Odoo instance.
-
Verify user access to journal entriesCheck user group assignments and access rights in Odoo: go to Settings > Users & Companies > Users, and review the security/access rights configuration for the Accounting app. Determine if standard users can create or edit journal entries.Affected if Users with access to the Accounting module can create, edit, or modify accounting journal entries without administrator oversight.
-
Inspect journal entries for injected contentAccess the Accounting dashboard > Journal Entries (or General Ledger), and review recent journal entry lines. Check fields such as 'Label', 'Description', 'Reference', and any memo/note fields for suspicious JavaScript patterns like '<script', 'javascript:', 'onerror=', or encoded payloads.Affected if Journal entries exist containing HTML, script tags, or suspicious-looking content that could indicate prior exploitation or lack of input sanitization.
You are affected if running Odoo Enterprise versions 13.0-15.0 with the Accounting module active and users have the ability to create or edit journal entries.
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 dataApply Odoo's security updates for this vulnerability and implement input sanitization on all journal entry fields that accept user input to prevent script injection.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-44461 — 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-2021-44461 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