Versions
0
>= 5.3.0, < 5.3.17
>= 5.2.0, < 5.2.20
>= 4.8.0, < 4.8.24
>= 5.1.0, < 5.1.6
>= 5.4.0, < 5.4.2
>= 3.8.0, < 3.8.34
< 4.1.40
5.8 beta 1
>= 5.2.0, < 5.8.1
>= 3.7.0, < 3.7.34
>= 5.1.0, < 5.1.18
>= 4.0.0, < 4.0.31
>= 4.5.0, < 4.5.22
>= 4.70,< 5.7.1
>= 5.4.0, < 5.4.15
>= 5.9.0, < 5.9.9
>= 5.0.0, < 5.0.21
>= 5.7.0, < 5.7.11
>= 6.3.0, < 6.3.3
< 5.8.3
>= 6.1.0, < 6.1.5
>= 5.5.0, < 5.5.14
>= 4.3.0, < 4.3.33
>= 6.2.0, < 6.2.4
>= 4.6.0, < 4.6.19
>= 4.7.0, < 4.7.18
>= 4.9.0, < 4.9.15
>= 4.4.0, < 4.4.32
5.8 beta 2
>= 4.5.0, < 4.5.31
>= 4.9.0, < 4.9.25
>= 6.0.0, < 6.0.7
>= 5.3.0, < 5.3.4
>= 3.9.0, < 3.9.32
>= 4.3.0, < 4.3.24
>= 4.2.0, < 4.2.37
>= 5.8.0, < 5.8.9
>= 5.6.0, < 5.6.13
>= 4.4.0, < 4.4.23
>= 6.4.0 < 6.4.2
>= 5.2.0, < 5.2.7
>= 4.7.0, < 4.7.28
>= 5.0.0, < 5.0.10
>= 5.6.0, < 5.7.1
>= 4.1.0, < 4.1.31
>= 4.2.0, < 4.2.28
>= 6.4.0, < 6.4.3
>= 4.6.0, < 4.6.28
>= 4.1.33, < 5.8.3
>= 5.0, < 5.8.0
>= 4.8.0, < 4.8.14
Recent CVEs
CVE-2024-31211
WordPress is an open publishing platform for the Web. Unserialization of instances of the `WP_HTML_Token` class allows for code execution via its `__destruct()` magic method. This issue was fixed in WordPress 6.4.2 on December 6th, 2023. Versions prior to 6.4.0 are not affected.
CVE-2024-31210
WordPress is an open publishing platform for the Web. It's possible for a file of a type other than a zip file to be submitted as a new plugin by an administrative user on the Plugins -> Add New -> Upload Plugin screen in WordPress. If FTP credentials are requested for installation (in order to move the file into place outside of the `uploads` directory) then the uploaded file remains temporary available in the Media Library despite it not being allowed. If the `DISALLOW_FILE_EDIT` constant is set to `true` on the site _and_ FTP credentials are required when uploading a new theme or plugin, then this technically allows an RCE when the user would otherwise have no means of executing arbitrary PHP code. This issue _only_ affects Administrator level users on single site installations, and Super Admin level users on Multisite installations where it's otherwise expected that the user does not have permission to upload or execute arbitrary PHP code. Lower level users are not affected. Sites where the `DISALLOW_FILE_MODS` constant is set to `true` are not affected. Sites where an administrative user either does not need to enter FTP credentials or they have access to the valid FTP credentials, are not affected. The issue was fixed in WordPress 6.4.3 on January 30, 2024 and backported to versions 6.3.3, 6.2.4, 6.1.5, 6.0.7, 5.9.9, 5.8.9, 5.7.11, 5.6.13, 5.5.14, 5.4.15, 5.3.17, 5.2.20, 5.1.18, 5.0.21, 4.9.25, 2.8.24, 4.7.28, 4.6.28, 4.5.31, 4.4.32, 4.3.33, 4.2.37, and 4.1.40. A workaround is available. If the `DISALLOW_FILE_MODS` constant is defined as `true` then it will not be possible for any user to upload a plugin and therefore this issue will not be exploitable.
CVE-2022-21662
WordPress is a free and open-source content management system written in PHP and paired with a MariaDB database. Low-privileged authenticated users (like author) in WordPress core are able to execute JavaScript/perform stored XSS attack, which can affect high-privileged users. This has been patched in WordPress version 5.8.3. Older affected versions are also fixed via security release, that go back till 3.7.37. We strongly recommend that you keep auto-updates enabled. There are no known workarounds for this issue.
CVE-2022-21663
WordPress is a free and open-source content management system written in PHP and paired with a MariaDB database. On a multisite, users with Super Admin role can bypass explicit/additional hardening under certain conditions through object injection. This has been patched in WordPress version 5.8.3. Older affected versions are also fixed via security release, that go back till 3.7.37. We strongly recommend that you keep auto-updates enabled. There are no known workarounds for this issue.
CVE-2022-21664
WordPress is a free and open-source content management system written in PHP and paired with a MariaDB database. Due to lack of proper sanitization in one of the classes, there's potential for unintended SQL queries to be executed. This has been patched in WordPress version 5.8.3. Older affected versions are also fixed via security release, that go back till 4.1.34. We strongly recommend that you keep auto-updates enabled. There are no known workarounds for this issue.
CVE-2022-21661
WordPress is a free and open-source content management system written in PHP and paired with a MariaDB database. Due to improper sanitization in WP_Query, there can be cases where SQL injection is possible through plugins or themes that use it in a certain way. This has been patched in WordPress version 5.8.3. Older affected versions are also fixed via security release, that go back till 3.7.37. We strongly recommend that you keep auto-updates enabled. There are no known workarounds for this vulnerability.