WordPress 4.7.2 Fixes Critical Vulnerabilities

Info

Author

Category

Date

January 27, 2017

WordPress receives additional security improvements with WordPress 4.7.2. This is a security release that includes fixes for 3 critical vulnerabilities and improvements for WordPress 4.7.1 and lower and is recommended for all WordPress users.

As always, Managed WordPress websites will be updated by 1&1 automatically. If you have installed WordPress yourself or use a standard installation from the 1&1 App Center, you can update to 4.7.2 from your WordPress Dashboard.SelectUpdates and click Update Now.

19 thoughts on “WordPress 4.7.2 Fixes Critical Vulnerabilities”

Warning: copy(/homepages/30/d574721670/htdocs/app574722482/wp-admin/includes/update-core.php): failed to open stream: Permission denied in /homepages/30/d574721670/htdocs/app574722482/wp-admin/includes/class-wp-filesystem-direct.php on line 257
The update cannot be installed because we will be unable to copy some files. This is usually due to inconsistent file permissions.: wp-admin/includes/update-core.php

the update to 4.7.2 will be rolled out by us to your installation very soon. In Managed WordPress you shouldn’t be able to do this manually at all. That’s our fault and we are very sorry! Will be fixed with the upcoming auto-update.

Is this issue resolved. I’m about to become a new customer of 1&1 for the Managed WordPress Plus and the issue mentionned in this thread is really bugging me. I’m not sure if choosing 1&1 is the best thing for me.

Those type of problems should be handle right away not 24hours later. This kind of delay can easily break some trust that I have with current customers of mine.

All my websites were updated to 4.7.2 and now none of them work and I am unable to fix the file mentioned in the error message because I do not have permission. Please fix your 4.7.2 rollout that broke all of my sites! Thank you.

Today I tried to access our website and got the following error: Warning: include_once(/homepages/35/d652293248/htdocs/app652293372/wp-content/plugins/cp-multi-view-calendar/classes/cp-base-class.inc.php): failed to open stream: No such file or directory in /homepages/35/d652293248/htdocs/app652293372/wp-content/plugins/cp-multi-view-calendar/cp-multi-view-calendar.php on line 17

Warning: include_once(): Failed opening ‘/homepages/35/d652293248/htdocs/app652293372/wp-content/plugins/cp-multi-view-calendar/classes/cp-base-class.inc.php’ for inclusion (include_path=’.:/usr/lib/php7.0′) in /homepages/35/d652293248/htdocs/app652293372/wp-content/plugins/cp-multi-view-calendar/cp-multi-view-calendar.php on line 17

Warning: include_once(/homepages/35/d652293248/htdocs/app652293372/wp-content/plugins/cp-multi-view-calendar/cp-main-class.inc.php): failed to open stream: No such file or directory in /homepages/35/d652293248/htdocs/app652293372/wp-content/plugins/cp-multi-view-calendar/cp-multi-view-calendar.php on line 18

Warning: include_once(): Failed opening ‘/homepages/35/d652293248/htdocs/app652293372/wp-content/plugins/cp-multi-view-calendar/cp-main-class.inc.php’ for inclusion (include_path=’.:/usr/lib/php7.0′) in /homepages/35/d652293248/htdocs/app652293372/wp-content/plugins/cp-multi-view-calendar/cp-multi-view-calendar.php on line 18

I am getting same error message as everyone else, posted below. I’m late to the game bc I’ve been out on a back injury, and just now able to get up and do somethings online, when I discovered the problem with my own personal site. Can I get this resolved here, or should I open a ticket? As per the other comments, I suspect my issue may be related to an plug-in that didn’t like any updates.

Warning: require_once(/homepages/2/d585968601/htdocs/clickandbuilds/ChanzillaWP/wp-includes/cache.php): failed to open stream: Permission denied in /homepages/2/d585968601/htdocs/clickandbuilds/ChanzillaWP/wp-includes/load.php on line 466

I can’t access the control panel bc I can’t get any pages to load. I did try PHP 5.6, 7, and 7.1, didn’t make a difference. I’m sure it’s a plug-in, but I can’t access my WP admin, all pages crash with the error I gave in my post.