WordPress before 4.9.9 and 5.x before 5.0.1 allows remote code execution because an _wp_attached_file Post Meta entry…
No fixed version listed yet.Check the vendor advisory. References ↓
WordPress before 4.9.9 and 5.x before 5.0.1 contains a flaw in which the _wp_attached_file Post Meta entry can be set to an arbitrary string, such as one ending in a .jpg?file.php substring. An attacker holding author privileges can achieve remote code execution by uploading a crafted image with PHP code embedded in its Exif metadata.
Official description · CVE.org
WordPress before 4.9.9 and 5.x before 5.0.1 allows remote code execution because an _wp_attached_file Post Meta entry can be changed to an arbitrary string, such as one ending with a .jpg?file.php substring. An attacker with author privileges can execute arbitrary code by uploading a crafted image containing PHP code in the Exif metadata. Exploitation can leverage CVE-2019-8943.
- 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 2 years after disclosure. Public exploit code (Metasploit) was available 1 day before disclosure.
- Public exploit codeMetasploit1 day before
- Disclosedday 0
- First seen exploitedVulnCheck KEV evidence+2 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.
- Log4j12 Jan 2022
- Ransomware: Night Sky12 Jan 2022