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

mediawiki

mediawiki

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 CVE identity is linked to the Lifecycle record MediaWiki. Use that record for publisher support phases and retirement dates.

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-2023-3550 25 Sep 2023 1.40.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2013-1817 20 Nov 2019 1.19.4; 1.20.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2013-1816 20 Nov 2019 1.19.4; 1.20.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2012-0046 29 Oct 2019 1.16 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-13258 4 Oct 2018 1.31 before 1.31.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-2018-0505 4 Oct 2018 before 1.31.1, 1.30.1, 1.29.3 and 1.27.5 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-2018-0504 4 Oct 2018 before 1.31.1, 1.30.1, 1.29.3 and 1.27.5 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-2018-0503 4 Oct 2018 before 1.31.1, 1.30.1, 1.29.3 and 1.27.5 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-2017-0370 13 Apr 2018 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-0369 13 Apr 2018 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-0368 13 Apr 2018 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-0367 13 Apr 2018 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-0366 13 Apr 2018 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-0365 13 Apr 2018 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-0364 13 Apr 2018 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-0363 13 Apr 2018 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-0362 13 Apr 2018 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2017-0361 13 Apr 2018 n/a No fixed version is explicitly recorded in the structured CVE data. Use CVE record

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.