WordPress Core <= 7.0.3 - Authenticated (Author+) Remote Code Execution via Malicious File Upload

WordPress Core is vulnerable to Remote Code Execution in multiple release branches, including versions 4.7.0 through 7.0.3. This is due to insufficient validation in the `WP_Image_Editor_Imagick::load()` image-processing path before passing uploaded files or streams to Imagick, which can interpret attacker-supplied image-like files as PostScript-family or compressed delegate formats based on magic bytes, format specifiers, or decompressed content rather than the WordPress-accepted extension. This makes it possible for authenticated attackers, with Author-level access and above, to upload a crafted file that is processed during attachment metadata generation and may trigger unsafe ImageMagick/Ghostscript behavior, resulting in remote code execution on sites using Imagick and Ghostscript. Unauthenticated exploitation is deployment-dependent and requires an additional public-upload plugin or theme path that sends attacker-supplied files through WordPress image metadata generation.

An attacker needs Author access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: updating to 4.7.35 is the step that ends it.

• Firewall
• Scanner
• Alerts