CVE-2024-31210
Vulnérabilité élevée dans wordpress-develop (WordPress)
Description
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.
Gravité et risque d'exploitation
CVE-2024-31210 obtient un score CVSS de 7.7/10, soit une gravité élevée. Selon le modèle EPSS, la probabilité qu'elle soit exploitée dans les 30 prochains jours est de 0.95 %, ce qui la place devant 60.4 % des CVE référencées.
Que faire ?
- Vérifiez si wordpress-develop (versions >= 5.8.0, < 5.8.9, >= 5.2.0, < 5.2.20, >= 6.4.0, < 6.4.3, >= 5.7.0, < 5.7.11, >= 5.1.0, < 5.1.18, >= 4.7.0, < 4.7.28, >= 4.5.0, < 4.5.31, >= 5.3.0, < 5.3.17, >= 5.5.0, < 5.5.14, >= 5.6.0, < 5.6.13, >= 4.6.0, < 4.6.28, >= 4.9.0, < 4.9.25, >= 6.3.0, < 6.3.3, >= 4.3.0, < 4.3.33, >= 6.1.0, < 6.1.5, >= 5.0.0, < 5.0.21, < 4.1.40, >= 6.2.0, < 6.2.4, >= 5.9.0, < 5.9.9, >= 4.2.0, < 4.2.37, >= 4.4.0, < 4.4.32, >= 5.4.0, < 5.4.15, >= 6.0.0, < 6.0.7, >= 4.8.0, < 4.8.24) est présent sur votre parc.
- Appliquez le correctif ou la version corrigée indiqués dans les références de l'éditeur.
- À défaut de correctif, limitez l'exposition (filtrage réseau, désactivation du composant).
- Automatisez la détection : les agents CVE Heimdall (gratuits, open source) corrèlent l'inventaire de vos serveurs avec la base CVE.