CVE-2026-124969: Optimole Flaw Risks WordPress Takeover

A security flaw in the Optimole image optimisation plugin for WordPress could let attackers without an account delete files from a website and, in the worst case, take full control of the site. The vulnerability, tracked as CVE-2026-124969, was published on 14 November 2026 and carries a CVSS score of 7.1, rated High.
The flaw affects all versions of the Optimole plugin up to and including version 4.2.19. It was assigned by Wordfence, the WordPress security company, which recorded the vulnerability as a deserialization weakness, listed as CWE-502. The researcher credited with finding the flaw is named in the CVE record as daroo. According to the record, the vendor was notified on 9 November and the issue was disclosed on 13 November.
How the flaw works
The problem sits in a function called replace_urls_in_value, which does not properly check file paths. Because of that weakness, an unauthenticated attacker can delete arbitrary files on the server. Deleting the right file, such as wp-config.php, which holds a WordPress site's database credentials, can easily lead to remote code execution, meaning an attacker could run their own code on the server.
There are two important limits on the attack. First, the PEAR Archive_Tar library must be present and loadable on the host. That library is common in official WordPress Docker images and many PHP distributions, so many sites will meet that condition. Second, the attacker cannot trigger the flaw on their own: after the attacker has staged a malicious payload in a comment, a site administrator must then use the plugin's Rename control on an attachment. Only that admin action completes the chain.
The CVSS vector for the flaw is CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:H. In plain terms, the attack can be launched over the network, it is not complex, it needs no privileges, but it does need a user to interact, and its main impact is on the availability and integrity of the site rather than on the confidentiality of its data. The vulnerability is not listed in CISA's Known Exploited Vulnerabilities catalogue, and no exploitation in the wild has been reported.
What site owners should do
Site owners running Optimole should update the plugin to the latest release. The vulnerability record references version 4.2.20, and updating removes the vulnerable code. Administrators should also check their sites for suspicious comments carrying unusual payloads, review recent use of the media Rename control, and look for missing or altered files, particularly wp-config.php.
The case is a reminder that image optimisation plugins, which handle uploaded media and file paths, can become a route into a site even when they are not the part of WordPress an owner thinks about most. Keeping plugins updated, limiting who can approve comments, and watching for unexpected admin actions are the practical steps that reduce the risk while the update is applied.