CVE-2024-31210: PHP file upload bypass via Plugin installer

Published Apr 4, 2024
·
Updated

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 DISALLOWFILEEDIT 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 DISALLOWFILEMODS 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 DISALLOWFILEMODS 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.

Affected Software

25 affected components
WordPress WordPress
WordPress WordPress<4.1.40
WordPress WordPress>=4.2<4.2.37
WordPress WordPress>=4.3<4.3.33
WordPress WordPress>=4.4<4.4.32
WordPress WordPress>=4.5<4.5.31
WordPress WordPress>=4.6<4.6.28
WordPress WordPress>=4.7<4.7.28
WordPress WordPress>=4.8<4.8.24
WordPress WordPress>=4.9<4.9.25
WordPress WordPress>=5.0<5.0.21
WordPress WordPress>=5.1<5.1.18
WordPress WordPress>=5.2<5.2.20
WordPress WordPress>=5.3<5.3.17
WordPress WordPress>=5.4<5.4.15
WordPress WordPress>=5.5<5.5.14
WordPress WordPress>=5.6<5.6.13
WordPress WordPress>=5.7<5.7.11
WordPress WordPress>=5.8<5.8.9
WordPress WordPress>=5.9<5.9.9
WordPress WordPress>=6.0<6.0.7
WordPress WordPress>=6.1<6.1.5
WordPress WordPress>=6.2<6.2.4
WordPress WordPress>=6.3<6.3.3
WordPress WordPress>=6.4.0<6.4.3

Event History

Apr 4, 2024
CVE Published
via MITRE·10:59 PM
Data Sourced
via MITRE·10:59 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·11:15 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-31210?

CVE-2024-31210 has a high severity due to the potential for unauthorized file uploads via the WordPress plugin installation process.

2

How do I fix CVE-2024-31210?

To fix CVE-2024-31210, update WordPress to version 6.4.4 or later immediately to patch the vulnerability.

3

Who is affected by CVE-2024-31210?

CVE-2024-31210 affects all WordPress installations up to version 6.4.3 that allow file uploads through the plugin installation interface.

4

What kind of files can be exploited in CVE-2024-31210?

CVE-2024-31210 can be exploited to upload malicious files that are not zip files, compromising the WordPress installation.

5

Is there a workaround for CVE-2024-31210?

As a temporary workaround for CVE-2024-31210, you can restrict plugin uploads by disabling the plugin upload feature in the WordPress dashboard.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203