WordPress MU 2.8.2

WordPress MU 2.8.2 has just been released. This is a security release with the same fix as the standalone WordPress.

WordPress 2.8.2 fixes an XSS vulnerability. Comment author URLs were not fully sanitized when displayed in the admin. This could be exploited to redirect you away from the admin to another site.

This release also fixes a number of other bugs, most notably the upgrade notice, but also fixes a number of other problems. See the timeline for a record of the latest activity.

Grab the new release from the download page or upgrade automatically from within WordPress MU.

18 thoughts on “WordPress MU 2.8.2

  1. Thanks for the quick release!

    I still have a problem with the upgrade. I upgraded yesterday and of course after that I’m still getting the “WordPress MU 2.8.1 is available! Please update.”. It’s not showing 2.8.2. If I try to update again it doesn’t work.

    Warning: copy(/var/www/wordpressmu/wp-content/upgrade/wordpress-mu-2.8.12/wordpress/wp-admin/includes/update-core.php) [function.copy]: failed to open stream: No such file or directory in /var/www/wordpressmu/wp-admin/includes/class-wp-filesystem-direct.php on line 131

    Could not copy files.

    Installation Failed

    What should I do now? If I download 2.8.2 and deploy it manually, should I make any change to the database?

    Best regards,

    Lobo Feroz

  2. Wonderful. I was waiting for it. Now I just wonder why the two MU setups that I manage don’t see the latest version yet. They still say “WordPress MU 2.8.1 is available. Upgrade now.” Is that prompt changing with a time lag? what time frame are we talking about? –oh, they are german language installs. Is that why it takes time?

    1. Not really because the translations are available elsewhere. If translations files were included in the release they would have to be updated before new releases, something that would be impossible with current resources available.

  3. On 2 Mu sites I run that were already on 2.8.1; using the upgrade button produced the same fatal error message that Lobo reported.

    However, updating The Old Fashioned Way solved the problem. And deeply increased my appreciation for the Update Button. 🙂

  4. hi
    give me ah mu plsssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssssss . full stats and fenrir

  5. I know that they have fixed a XSS vulnerability in the new version. Any other significant improvement in this new version?

Leave a Reply

%d bloggers like this:

By continuing to use the site, you agree to the use of cookies. more information

The cookie settings on this website are set to "allow cookies" to give you the best browsing experience possible. If you continue to use this website without changing your cookie settings or you click "Accept" below then you are consenting to this.