In WordPress 4.9.7, plugins uploaded via the admin area are not verified as being ZIP files
No fixed version listed yet.Check the vendor advisory. References ↓
In WordPress 4.9.7, the plugin upload handler in the admin area does not verify that an uploaded plugin is a ZIP file, so a PHP file can be placed in a predictable wp-content/uploads location when extraction fails. An attacker who already holds the capability to upload plugins can then execute that PHP file, but only in limited cases where the wp-content/plugins directory has been locked down so that arbitrary plugin ZIPs cannot be installed.
Official description · CVE.org
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.
- Exploited
- Yes, in VulnCheck KEV
- Reports
- 0
- Tactics
- 0/15
Exploitation timelineDated milestones for a CVE: when it was disclosed, when exploit code became public, when exploitation was confirmed, and when threat reports named it.
First seen exploited 8 years after disclosure.
- Disclosedday 0
- First seen exploitedVulnCheck KEV evidence+8 yrs
What security researchers reported
Not named in any threat report yetAlso mentioned in 2 community threat pulses (AlienVault OTX)
Weaker evidencePulses are indicator collections that anyone can publish. A mention is not confirmation of exploitation.