← Search results
CVE-LINKED INVENTORY25 SECURITY RECORDS
Microsoft
Microsoft SharePoint Foundation
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 SharePoint Foundation. 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-2020-1289 | 9 Jun 2020 | 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-2020-0931 | 15 Apr 2020 | 2013 Service Pack 1; 2016; 2019; 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-2020-0892 | 12 Mar 2020 | 2013 Service Pack 1; 2016; 2019; 2010 Service Pack 2; 2019 for 32-bit editions; 2019 for 64-bit editions; 2019 for Mac; 2016 for Mac | 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-1443 | 12 Nov 2019 | 2010 Service Pack 2; 2013 Service Pack 1; 2016; 2019 | 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-1330 | 10 Oct 2019 | 2013 Service Pack 1; 2016; 2019 | 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-1329 | 10 Oct 2019 | 2010 Service Pack 2; 2013 Service Pack 1; 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-1328 | 10 Oct 2019 | 2010 Service Pack 2; 2013 Service Pack 1; 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-1070 | 10 Oct 2019 | 2013 Service Pack 1; 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-1296 | 11 Sep 2019 | 2013 Service Pack 1; 2016; 2019 | 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-1295 | 11 Sep 2019 | 2010 Service Pack 2; 2013 Service Pack 1; 2016; 2019 | 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-1262 | 11 Sep 2019 | 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-2019-1261 | 11 Sep 2019 | 2013 Service Pack 1; 2016; 2019 | 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-1260 | 11 Sep 2019 | 2010 Service Pack 2; 2013 Service Pack 1; 2016; 2019 | 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-1259 | 11 Sep 2019 | 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-2019-1257 | 11 Sep 2019 | 2010 Service Pack 2; 2013 Service Pack 1; 2016; 2019 | 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-0963 | 16 May 2019 | 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-2019-0958 | 16 May 2019 | 2013 Service Pack 1; 2019 | 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-0956 | 16 May 2019 | 2013 Service Pack 1; 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-0952 | 16 May 2019 | 2013 Service Pack 1; 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-0951 | 16 May 2019 | 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-2019-0950 | 16 May 2019 | 2013 Service Pack 1; 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-0949 | 16 May 2019 | 2013 Service Pack 1; 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-0830 | 9 Apr 2019 | 2013 Service Pack 1; 2016; 2019 | 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-0778 | 9 Apr 2019 | 2013 Service Pack 1; 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-0670 | 6 Mar 2019 | 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 ↗ |
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.