Vulnerabilities

Security fix · CVE-2021-26947

[IMP] web: StaticList: support CLEAR (5) orm command Before this commit, the StaticList didn't expose a way to apply a CLEAR command (command 5), i.e.

Published Apr 25, 2023 · catalog updated Jun 17, 2026 · Odoo Odoo

Check if you run it

No confirmed exploitation is on record for CVE-2021-26947. EPSS is 1.40%. 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
Medium6.1
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
1.40%
Remediation
Fix linked
Affected products
cpe odoo/odoo

[IMP] web: StaticList: support CLEAR (5) orm command Before this commit, the StaticList didn't expose a way to apply a CLEAR command (command 5), i.e. to empty the relation. This commit adds a function to do so, and adds the support of the CLEAR command in . Note: since [1], onchange no longer returns CLEAR commands (it only returns commands from 0 to 4). So this commit adapts a few historical tests that still simulated onchanges returning a CLEAR command as first command. Request for task~5350021 [1] https://github.com/odoo/odoo/pull/119510 Part-of: odoo/odoo#249054 Related: odoo/enterprise#1

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-2021-26947

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-2021-26947. EPSS is 1.40%. 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-79: Cross-site Scripting (XSS). EPSS 1.40%. 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.

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

  • Feb 16, 2026 · cited

    [IMP] web: StaticList: support SET (6) orm command

    [IMP] web: StaticList: support SET (6) orm command Before this commit, `_applyCommands` didn't support SET command (command 6). As a consequence, this command had to be special-cased in `_preprocessX2manyChanges`, and in an override of `Record` in the ai_fields addon [1]. With this commit, the SET command is now supported in `_applyCommands`, and a `set()` function has been added on StaticList for convenience. Note: since [2], onchange no longer returns SET commands (it only returns commands from 0 to 4). So this commit adapts a historical test that still simulated an onchange returning a SET command as first command. No task, but followup of [3] [1] https://github.com/odoo-dev/enterprise/blob/366f0376644d4aecd239378782d2db896ea7bf9f/ai_fields/static/src/model/relational_model/record.js#L26 [2] https://github.com/odoo/odoo/pull/119510 [3] https://github.com/odoo/enterprise/pull/830…
    https://github.com/odoo/odoo/commit/ee73ee2a3920798c4637174485aed830243ed96c
  • Feb 16, 2026 · cited

    [IMP] web: StaticList: support CLEAR (5) orm command

    [IMP] web: StaticList: support CLEAR (5) orm command Before this commit, the StaticList didn't expose a way to apply a CLEAR command (command 5), i.e. to empty the relation. This commit adds a `clear()` function to do so, and adds the support of the CLEAR command in `_applyCommands`. Note: since [1], onchange no longer returns CLEAR commands (it only returns commands from 0 to 4). So this commit adapts a few historical tests that still simulated onchanges returning a CLEAR command as first command. Request for task~5350021 [1] https://github.com/odoo/odoo/pull/119510 Part-of: odoo/odoo#249054 Related: odoo/enterprise#107694
    https://github.com/odoo/odoo/commit/9087aed90e0e009fd98024e60614e28d15d0ff40

Timeline

Detection, updates, and resolution for this record.

  1. Apr 25, 2023 · Catalog

    Detected

    Cross-site scripting (XSS) issue Odoo Community 15.0 and earlier and Odoo Enterprise 15.0 and earlier, allows remote attackers to inject arbitrary web script in the browser of a victim, via a crafted link.

  2. Jun 16, 2026 · Catalog

    Updated

    Cross-site scripting (XSS) issue Odoo Community 15.0 and earlier and Odoo Enterprise 15.0 and earlier, allows remote attackers to inject arbitrary web script in the browser of a victim, via a crafted link.

  3. Jun 17, 2026 · NIST NVD

    Updated

    Cross-site scripting (XSS) issue Odoo Community 15.0 and earlier and Odoo Enterprise 15.0 and earlier, allows remote attackers to inject arbitrary web script in the browser of a victim, via a crafted link.

Sources

  • CVE.orgVulnerability recordCVE-2021-26947

    Official CVE identifier

    cve.org
  • FIRST EPSSExploitation probabilityCVE-2021-26947

    30-day exploitation probability 1.4%

    first.org
  • NIST NVDVulnerability recordCVE-2021-26947

    Cross-site scripting (XSS) issue Odoo Community 15.0 and earlier and Odoo Enterprise 15.0 and earlier, allows remote attackers to inject arbitrary web script in the browser of a victim, via a crafted link.

    nvd.nist.gov
  • Odoo SecurityVendor advisoryCVE-2021-26947

    Odoo or OpenERP product vulnerability. Vendor discussion stays on the Odoo tracker.

    github.com
  • Odoo Community GitGit security fix referenceCVE-2021-26947

    [IMP] web: StaticList: support SET (6) orm command Before this commit, didn't support SET command (command 6). As a consequence, this command had to be special-cased in , and in an override of in the ai_fields addon [1]. With this commit, the SET command is now supported in , and

    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.