Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY232 SECURITY RECORDS

xwiki

XWiki Platform

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2022-36090 8 Sep 2022 >= 1.1, < 13.10.5; >= 14.0, < 14.3-RC-1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-31166 7 Sep 2022 >= 11.3.7, < 13.10.4; >= 14.0-rc-1, < 14.2-rc-1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-31167 7 Sep 2022 >= 5.0, < 12.10.11; >= 13.0, < 13.4.6; >= 13.10, < 13.10.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-29258 31 May 2022 >= 5.4.4, <= 6.0-milestone-2; >= 6.0-milestone-2, < 12.10.11; >= 13.0.0, < 13.4.7; >= 13.5.0, < 13.10.3 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-29251 25 May 2022 >= 6.2.4, < 12.10.11; >= 13.0, < 13.4.7; >= 13.5, < 13.10.3 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-29252 25 May 2022 >= 5.3-milestone-2, < 12.10.11; >= 13.0, < 13.4.7; >= 13.5, < 13.10.3 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-29253 25 May 2022 >= 8.3-rc-1, < 13.10.3 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-29161 5 May 2022 < 13.10.6; >= 14.0.0, < 14.3.1; >= 14.4.0, < 14.4-rc-1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-24820 8 Apr 2022 < 8.4.5, < 10.11.8, < 11.3.1, < 13.6-rc-1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-24819 8 Apr 2022 < 4.3 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-24821 8 Apr 2022 > 3.1M1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-23622 9 Feb 2022 >= 2.6.1, < 12.10.11; >= 13.0.0, < 13.4.7; >= 13.10.0, < 13.10.3 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-23621 9 Feb 2022 >= 13.6.0, < 13.7-rc-1; >= 13.0.0, < 13.4.3; < 12.10.9 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-23620 9 Feb 2022 >= 6.2-rc-1, < 13.6 13.6-rc-1. Update reference ↗
CVE-2022-23619 9 Feb 2022 >= 13.6.0, < 13.6RC1; >= 13.0.0, < 13.4.1; < 12.10.9 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-23618 9 Feb 2022 >= 13.0.0, < 13.3RC1; < 12.10.7 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-23617 9 Feb 2022 >= 13.0.0, < 13.2-rc-1; < 12.10.6 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-23616 9 Feb 2022 > 3.1M1, < 13.1RC1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2022-23615 9 Feb 2022 >= 1.0, < 13.0 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-43841 4 Feb 2022 < 12.10.6; >= 13.0, < 13.3RC1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-32732 4 Feb 2022 < 12.10.5 ; >= 13.0, < 13.2RC1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-32731 1 Jul 2021 >= 13.1RC1, <= 13.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-32730 1 Jul 2021 < 12.10.5; >= 13.0, <= 13.1 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-32729 1 Jul 2021 > 11.6RC1, < 12.6.8; >= 12.10.0, < 12.10.4 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-32620 28 May 2021 < 11.10.13; >= 12.6.0, < 12.6.7; >= 12.10.0, < 12.10.2 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-32621 28 May 2021 < 12.6.7; >= 12.10.0, < 12.10.3 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-29459 20 Apr 2021 < 12.6.3; >= 12.6.4, < 12.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-21380 23 Mar 2021 < 12.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-21379 12 Mar 2021 >= 11.4.0, < 11.10.11; >= 12.0.0, < 12.6.3; >= 12.7.0, < 12.8-rc-1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-15252 16 Oct 2020 >= 12.0, < 12.5; < 11.10.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-15171 10 Sep 2020 <11.10.5; >=12.0.0, <12.2.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-11057 12 May 2020 >= 7.2, < 11.10.3 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.