SharePoint security fixes released with June 2021 PU and offered through Microsoft Update

Below are the security fixes for the SharePoint OnPrem versions released this month.

Important:
SharePoint Foundation security fixes also have to be applied on SharePoint Server installations.
SharePoint Server security fixes also have to be applied on Project Server installations.

SharePoint 2013 Suite:

  • KB 5001962 – SharePoint Foundation 2013 (core component)
  • KB 5001939 – SharePoint Foundation 2013
  • KB 4011698 – InfoPath Forms Services for SharePoint 2013
  • KB 5001954 – SharePoint Server 2013 (core component)
  • KB 5001956 – Office Web Apps Server 2013
  • Microsoft Support recommends to install the complete June 2021 CU for SharePoint 2013 rather than individual security fixes

SharePoint 2016 Suite:

  • KB 5001946 – SharePoint Server 2016 (language independent)
  • KB 5001922 – SharePoint Server 2016 (language dependent)

SharePoint 2019 Suite:

  • KB 5001944 – SharePoint Server 2019 (language independent)
  • KB 5001945 – SharePoint Server 2019 (language independent)

Office Online Server:

  • KB 5001943 – Office Online Server
See the Security Update Guide below for more details about the relevant fixes:

More information:

Please ensure to have a look at the SharePoint Patching Best Practices before applying new fixes.
 

20 Comments


  1. hi Stefan ,
    i’m using a thirdd party software for management updates for my SharePoint 2013 foundation server it lists :
    KB 5001962 – SharePoint Foundation 2013 (core component)
    KB 5001939 – SharePoint Foundation 2013

    as an applicaple updates , but it also lists :

    KB 5001954 – SharePoint Server 2013 (core component)

    as applicable , i beleive i need only the above two for the foundation version and no need to install the third one (KB 5001954 – SharePoint Server 2013 (core component) , am right ?

    Reply

    1. Hi Hazem,
      I do not have a SharePoint Foundation machine around to verify.
      My suggestion would be to try to install all 3.
      If one does not apply you will get a message right away and it will not install.
      Cheers,
      Stefan

      Reply

  2. Hi stefan, It looks like this security fixes does break publication sites on sharepoint 2013… Same issue in two OOB 2013 farms:
    Getting Error Message for Exception System.Web.HttpUnhandledException (0x80004005): Exception of type ‘System.Web.HttpUnhandledException’ was thrown. —> System.Web.HttpException (0x80004005): The DataSourceID of ‘V4QuickLaunchMenu’ must be the ID of a control of type IHierarchicalDataSource. A control with ID ‘QuickLaunchSiteMap’ could not be found.
    at System.Web.UI.WebControls.HierarchicalDataBoundControl.GetDataSource()
    at System.Web.UI.WebControls.HierarchicalDataBoundControl.ConnectToHierarchicalDataSource()
    at System.Web.UI.WebControls.HierarchicalDataBoundControl.OnLoad(EventArgs e)
    at System.Web.UI.Control.LoadRecursive()
    at System.Web.UI.Control.LoadRecursive()
    at System.Web.UI.Control.LoadRecursive()
    at System.Web.UI.Control.LoadRecursive()
    at System.Web.UI.Control.LoadRecursive()
    at System.Web.UI.Control.LoadRecursive()
    at System.Web.UI.Control.LoadRecursive()
    at System.Web.UI.Control.LoadRecursive()
    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    at System.Web.UI.Page.HandleError(Exception e)
    at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    at System.Web.UI.Page.ProcessRequest(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
    at System.Web.UI.Page.ProcessRequest()
    at System.Web.UI.Page.ProcessRequest(HttpContext context)
    at Microsoft.SharePoint.Publishing.TemplateRedirectionPage.ProcessRequest(HttpContext context)
    at System.Web.HttpApplication.CallHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

    At least, none of the other site type are affected.

    Reply

    1. Hi Ramon,
      I would recommend to open a support case with Microsoft to ensure that this will be investigated.
      Thanks,
      Stefan

      Reply

      1. Hi Ramon Garcia, Ho Stefan, did you solve the problem? I have the same issue on 4 farms. The security fixes does break sites on Sharepoint 2013.
        Thanks

        Reply

    2. Hi Ramon, did you solve the problem? Same issue here After the KB 5001954 update on Server Farm Sharepoint 2013.Thanks

      Reply

    3. Hi Ramon,
      did you fix the issue?
      Thanks

      Reply

    1. Hi Christian,
      that is not correct. 5001954 is included in 5001961. 5001961 is the uber package while 5001954 is a single security fix.
      Its always recommended to install the full CU rather than just the security fixes.
      Cheers,
      Stefan

      Reply

  3. Hey Stefan,

    We encountered an issue when we installed the latest updates on our SharePoint app server. After the updates the server boots into a black screen after login screen.

    We are running SharePoint 2016 on Windows Server 2012 R2. Have you heard of this issue or know any workarounds?

    Reply

  4. Hi Stefan,
    security fixes
    KB 5001954 – SharePoint Server 2013 (core component) does break Sharepoint 2013 sites ( 2 Sharepoint farms).Same errors as Ramon Garcia.

    Thanks

    Reply

  5. Hi Stefan,
    security fixes kb5001954 does break sites on sharepoint 2013. I have two farms affected.
    Errors are:
    Unexpected Exception in file C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\15\Template\Layouts\EditingMenu\SiteAction.xml: Object reference not set to an instance of an object.
    Unexpected System.Web.HttpException: The DataSourceID of ‘TopNavigationMenu’ must be the ID of a control of type IHierarchicalDataSource. A control with ID ‘topSiteMap’ could not be found. at System.Web.UI.WebControls.HierarchicalDataBoundControl.GetDataSource() at System.Web.UI.WebControls.HierarchicalDataBoundControl.ConnectToHierarchicalDataSource() at System.Web.UI.WebControls.HierarchicalDataBoundControl.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive()
    Unexpected … System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)

    Reply

    1. Hi Lin,
      I would recommend ton install the full June 2021 CU and run PSConfig afterwards.
      If this does not help my recommendation would be to open a support ticket with Microsoft to get this analyzed.
      Cheers,
      Stefan

      Reply

  6. Hi Stefan,

    We are getting below error on 3 of our SharePoint 2013 forms after updating June 2021 patch

    Application error when access /Pages/home.aspx, Error=The DataSourceID of ‘V4QuickLaunchMenu’ must be the ID of a control of type IHierarchicalDataSource. A control with ID ‘QuickLaunchSiteMap’ could not be found. at System.Web.UI.WebControls.HierarchicalDataBoundControl.GetDataSource() at System.Web.UI.WebControls.HierarchicalDataBoundControl.ConnectToHierarchicalDataSource() at System.Web.UI.WebControls.HierarchicalDataBoundControl.OnLoad(EventArgs e) at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.Web.UI.Control.LoadRecursive() at System.We… 9c4cd59f-ae98-50df-e9fe-3a0b8d96abc3

    Reply

    1. Hi Sanjeeth,
      I would recommend ton install the full June 2021 CU and run PSConfig afterwards.
      If this does not help my recommendation would be to open a support ticket with Microsoft to get this analyzed.
      Cheers,
      Stefan

      Reply

      1. Hi Sanjeeth, my companies 2 SharePoint 2013 farms also getting the same errors as yours. Have you tried installed the full June 2021 CU and does the issue resolved after that?

        Reply

  7. As a note i am getting the two following errors when trying to run the PSCONFIG on Sharepoint Foundations 2013.

    Insufficient SQL database permissions for user ‘Name: NT AUTHORITY\SYSTEM SID: S-1-5-18 ImpersonationLevel: None’ in database ‘SharePoint_Config’

    An exception of type System.Data.SqlClient.SqlException was thrown. Additional
    exception information: To revoke or deny grantable privileges, specify the CASCA
    DE option.

    Reply

    1. Hi Brett, this indicates that you are running PSConfig in context of the system account of the machine and not in context of an interactive user.
      Is it (e.g.) running from a Task Scheduler?

      Please try to logon to the machine with the farm account and execute PSConfig from a command prompt in context of this user.

      Reply

  8. HI Stephan,

    Facing the same issue as Ramon. Have installed June 2013 patch in our 4 app servers. Site breaking with similar issue mentioned by Ramon. Any fix for this. Please help us on this

    Reply

    1. Hi Gowtham,
      did you install just the security fix or the complete June CU?
      The issue should be resolved after installing the complete June CU.
      Cheers,
      Stefan

      Reply

Leave a Reply to Stefan Goßner Cancel reply

This site uses Akismet to reduce spam. Learn how your comment data is processed.