Release Notes for WordPress

Important Note

1. Starting from this version, WordPress no longer supports retaining or restoring package-related data after an uninstallation.

Compatibility and Installation

1. PHP 7.4 is required.
2. Apache 2.4 is required.

What's New

1. Updated to version 5.8.3.

Fixed Issues

1. Fixed multiple security vulnerabilities (CVE-2021-39200, CVE-2021-39201, CVE-2022-21663, CVE-2022-21662, CVE-2022-21664, CVE-2022-21661).
2. Fixed an issue where users might encounter the 500 error after updating the package.
3. Fixed an issue where users might encounter the 404 error after updating the package.
4. Minor bug fixes.

What's New

1. Updated to version 5.7.2.

Fixed Issues

1. Fixed a security vulnerability (CVE-2021-29450).
2. Minor bug fixes.

Fixed Issue

1. Fixed an issue where a database connection error might occur when users installed WordPress and configured virtual hosts on DSM for the first time.

Important Note

1. This update is expected to be available in all regions within the next few days. The actual time of release may vary slightly depending on regions.

What's new

1. Updated to version 5.5.3.
2. PHP 7.3 is required.

Fixed issues

1. Fixed multiple security vulnerabilities (CVE-2020-4047, CVE-2020-4049, CVE-2020-4050, CVE-2020-4048, CVE-2020-4046).

What's New

1. Updated to version 5.3.2.

What's new

1. Updated to version 5.2.4.

Fixed issues

1. Fixed multiple security vulnerabilities.

1. Fixed multiple vulnerabilities regarding WordPress ( CVE-2018-1000773, CVE-2018-20147, CVE-2018-20148, CVE-2018-20149, CVE-2018-20150, CVE-2018-20151, CVE-2018-20152, CVE-2018-20153, CVE-2019-8942, CVE-2019-8943, CVE-2019-9787).
2. Upgraded to version 5.2.0.

1. Fixed a vulnerability regarding WordPress (CVE-2018-14028)

Updated to version 4.9.7 to fix multiple vulnerabilities regarding WordPress (CVE-2018-10100, CVE-2018-10101, CVE-2018-10102, CVE-2018-12895).

1. Upgraded to version 4.9.4 to fix multiple security vulnerabilities regarding WordPress (CVE-2018-6389, CVE-2018-5776).

1. Enhanced overall stability.
2. Upgraded to version 4.9.1 to address multiple vulnerabilities(CVE-2017-17093, CVE-2017-17094, CVE-2017-17091, CVE-2017-17092, CVE-2017-16510, CVE-2016-9263, CVE-2017-14990, CVE-2017-14720, CVE-2017-14726, CVE-2017-14725, CVE-2017-14718, CVE-2017-14724, CVE-2017-14723, CVE-2017-14721, CVE-2017-14722, CVE-2017-14719).

Fixed an issue where data loss might occur in WordPress after the package installation retry.

Fixed an issue where the update of WordPress might fail after the change in user password for the database in MariaDB 5.

1. Upgraded to be compatible with MariaDB 10.
2. Fixed an issue where WordPress cannot be started after the package database password is changed via MariaDB.
3. Upgraded to version 4.7.5 to address multiple vulnerabilities.(https://wordpress.org/news/2017/05/wordpress-4-7-5/)

1. Fix an issue where downloading the plugin fails under some circumstances
2. You can find WordPress in the search bar of DSM now.

Upgraded to version 4.7.3 to address multiple vulnerabilities (CVE-2017-6814, CVE-2017-6815, CVE-2017-6816, CVE-2017-6817, CVE-2017-6818 and CVE-2017-6819).

1. Updated WordPress to 4.7.2.
2. Fixed an issue where some files might be lost after update.

1. Upgraded to 4.6.1.
2. Upgrade plugin photo station TinyMCE.

1. Upgraded to version 4.5.3.
2. Fixed an issue where the plugin akismet may be downgraded upon the package upgrade.

1. Upgraded to version 4.5.2 to address multiple vulnerabilities (CVE-2016-2221, CVE-2016-2222, CVE-2016-4566, CVE-2016-4567).
2. Fixed an issue where web installation might fail when installing via HTTPS.

1. Fixed an issue where .htaccess could not be backed up in a MariaDB database backup.

1. Updated the backend server to ngnix for enhanced performance.

1. Upgraded WordPress to 4.2.4 to address multiple security vulnerabilities (CVE-2015-5622, CVE-2015-5623, CVE-2015-2213, CVE-2015-5730, CVE-2015-5731, CVE-2015-5732, CVE-2015-5733, and CVE-2015-5734).

1. Upgraded WordPress to 4.1.5 to address multiple security vulnerabilities (CVE-2015-3438, CVE-2015-3439, and CVE-2015-3440)

1. Upgraded WordPress to 4.1.4 to address a cross-site scripting (XSS) vulnerability, which could enable commenters to compromise a site.

1. Upgraded WordPress to 4.1.

1. Upgraded version to 4.0.1 to address multiple critical security vulnerabilites.

1. Changing the password for MariaDB will now automatically update the password for this package.

1. Certified by Synology Trust Level.

Improvements

1. Upgraded WordPress to version 3.9.2.

Fixed Issues

1. Upgraded to version 3.8.2 to address several security issues.

1. Disabled pingbacks option for security purpose.

1. Upgraded to WordPress 3.8.

Upgraded to version 3.5.1.

1. Update WordPress package to 3.4.