← Search results
CVE-LINKED INVENTORY36 SECURITY RECORDS
Microsoft Corporation
Microsoft SharePoint
Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.
This CVE identity is linked to the Lifecycle record Microsoft SharePoint. 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
| CVE | Published | Affected versions | Fixed version information | Publisher evidence |
|---|---|---|---|---|
| CVE-2019-0557 | 8 Jan 2019 | Enterprise Server 2016 | 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-2019-0556 | 8 Jan 2019 | Enterprise Server 2013 Service Pack 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-8650 | 12 Dec 2018 | Enterprise Server 2016 | 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-8580 | 12 Dec 2018 | Enterprise Server 2013 Service Pack 1; Enterprise Server 2016; Foundation 2010 Service Pack 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-2018-8578 | 14 Nov 2018 | Enterprise Server 2013 Service Pack 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-8518 | 10 Oct 2018 | Enterprise Server 2013 Service Pack 1; Enterprise Server 2016 | 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-8498 | 10 Oct 2018 | Enterprise Server 2013 Service Pack 1; Enterprise Server 2016 | 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-8488 | 10 Oct 2018 | Enterprise Server 2013 Service Pack 1; Enterprise Server 2016 | 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-8480 | 10 Oct 2018 | Enterprise Server 2016 | 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-8428 | 13 Sep 2018 | Enterprise Server 2013 Service Pack 1; Enterprise Server 2016 | 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-8323 | 11 Jul 2018 | Enterprise Server 2013 Service Pack 1; Enterprise Server 2016 | 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-8300 | 11 Jul 2018 | Enterprise Server 2016; Foundation 2013 Service Pack 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-8299 | 11 Jul 2018 | Enterprise Server 2013 Service Pack 1; Enterprise Server 2016; Foundation 2013 Service Pack 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-8252 | 14 Jun 2018 | Enterprise Server 2016; Foundation 2013 Service Pack 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-8156 | 9 May 2018 | Enterprise Server 2016; 2010 Service Pack 2; 2013 Service Pack 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-8155 | 9 May 2018 | Enterprise Server 2016; Foundation 2013 Service Pack 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-1034 | 12 Apr 2018 | Enterprise Server 2016 | 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-1014 | 12 Apr 2018 | Enterprise Server 2013 Service Pack 1; Enterprise Server 2016 | 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-1005 | 12 Apr 2018 | Enterprise Server 2013 Service Pack 1; Enterprise Server 2016 | 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-0947 | 14 Mar 2018 | Microsoft SharePoint Foundation 2013 SP1 and Microsoft SharePoint Enterprise Server 2016 | 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-0944 | 14 Mar 2018 | Microsoft Project Server 2013 SP1 and Microsoft SharePoint Enterprise Server 2016 | 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-0923 | 14 Mar 2018 | Microsoft SharePoint Enterprise Server 2016 | 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-0921 | 14 Mar 2018 | Microsoft SharePoint Enterprise Server 2016 | 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-0917 | 14 Mar 2018 | Microsoft SharePoint Enterprise Server 2016 | 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-0916 | 14 Mar 2018 | Microsoft Project Server 2013 SP1 and Microsoft SharePoint Enterprise Server 2016 | 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-0915 | 14 Mar 2018 | Microsoft Project Server 2013 SP1 and Microsoft SharePoint Enterprise Server 2016 | 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-0914 | 14 Mar 2018 | Microsoft Project Server 2013 SP1 and Microsoft SharePoint Enterprise Server 2016 | 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-0913 | 14 Mar 2018 | Microsoft Project Server 2013 SP1 and Microsoft SharePoint Enterprise Server 2016 | 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-0912 | 14 Mar 2018 | Microsoft Project Server 2013 SP1 and Microsoft SharePoint Enterprise Server 2016 | 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-0911 | 14 Mar 2018 | Microsoft Project Server 2013 SP1 and Microsoft SharePoint Enterprise Server 2016 | 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-0910 | 14 Mar 2018 | Microsoft Project Server 2013 SP1 and Microsoft SharePoint Enterprise Server 2016 | 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-0909 | 14 Mar 2018 | Microsoft Project Server 2013 SP1 and Microsoft SharePoint Enterprise Server 2016 | 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-0790 | 10 Jan 2018 | Microsoft SharePoint Foundation 2010, Microsoft SharePoint Server 2013 and Microsoft SharePoint Server 2016 | 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-11936 | 12 Dec 2017 | Microsoft SharePoint Enterprise Server 2016 | 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-8551 | 15 Jun 2017 | Microsoft Project Server 2013 Service Pack 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-2017-8514 | 15 Jun 2017 | Microsoft SharePoint Enterprise Server 2016 | 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.