Arbitrary file upload in WordPress
CVE-2018-14028
In WordPress 4.9.7, plugins uploaded via the admin area are not verified as being ZIP files. This allows for PHP files to be uploaded. Once a PHP file is uploaded, the plugin extraction fails, but the PHP file remains in a predictable wp-content/uploads location, allowing for an attacker to then execute the file. This represents a security risk in limited scenarios where an attacker (who does have the required capabilities for plugin uploads) cannot simply place arbitrary PHP code into a valid plugin ZIP file and upload that plugin, because a machine's wp-content/plugins directory permissions were set up to block all new plugins.
Vulnerability class: Unrestricted File Upload
Published · last modified .
CVSS v3 metric
CVSS v3 base score 7.2 (High). Vector: CVSS:3.0/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H.
EPSS exploit prediction
EPSS 0.152, 96.8th percentile (scored ); unchanged over 30 days. About EPSS.
Affected products
- WordPress — versions 4.9.7
Weakness classification (CWE)
Public exploits and proof-of-concept code
Also mentioned in 2 other repositories (20142995/nuclei-templates, ARPSyndicate/cvemon). These reference the CVE in a list, notes or a scanner and are not exploit code for it.
References
- core.trac.wordpress.org/ticket/44710 (Third Party Advisory)
- github.com/rastating/wordpress-exploit-framework/pull/52 (Third Party Advisory)
- rastating.github.io/unrestricted-file-upload-via-plugin-uploader-in-wordpress/ (Third Party Advisory)
- www.securityfocus.com/bid/105060 (Third Party Advisory, VDB Entry, vdb-entry)