Over 40,000 web sites working a weak model of a well-liked WordPress plugin could possibly be vulnerable to being hijacked by hackers.
The Submit SMTP plugin is an add-on utilized by roughly 400,000 WordPress-powered web sites to enhance the reliability and safety of their e mail supply. The plugin has confirmed common partially due to its advertising that presents it as a extra dependable and full-featured alternative to the default e mail performance constructed into WordPress.
In keeping with a report by Patchstack, an moral hacker responsibly disclosed a critical vulnerability within the Submit SMTP plugin.
The flaw allowed web site customers who ought to solely have low privileges, resembling Subscribers, to intercept any e mail despatched by the WordPress web site, together with password reset emails to any person. Utilizing this info, a low-privileged person would have the ability to seize management of an Administrator-level account, resulting in a full web site takeover.
Saad Iqbal of WPExperts, the developer of the plugin, took the report significantly and supplied a possible patch inside three days which was confirmed to resolve the vulnerability – which had been given the title CVE-2025-24000.
On June 11, Iqbal launched model 3.3.0 of the Submit SMTP plugin, which included the patch for the flaw.
You may suppose this can be a joyful finish to the story – however it’s not.
You see, the issue is that in accordance with WordPress.org, over 10% of the plugin’s 400,000+ energetic customers are nonetheless working the weak model 3.1 (proven right here in purple).
As Bleeping Laptop studies, a worrying 24.2% of websites (nearly 100,000) are nonetheless working Submit SMTP model 2.x..x – which leaves them open to much more recognized vulnerabilities and safety flaws.
So, what are you able to do?
Effectively, first issues first. In the event you administer a WordPress web site, replace its plugins.
Any out-of-date plugins will be up to date by visiting your wp-admin dashboard inside WordPress. You’ll be able to even, in case you are snug, set WordPress plugins to routinely replace when new variations change into accessible.
Moreover, ask your self what you might be doing to harden your web site and WordPress set up? For example, are you limiting entry to your web site’s admin interface to particular IP addresses? Do you’ve multi-factor authentication in place? Have you ever checked out what plugins and themes you’ve put in in your web site, and eliminated any which are not required?
Patching is clearly smart and needs to be undertaken on the earliest alternative, however always remember that further layers of safety can transcend patches – and maybe be extra proactive in defending your methods from assault.
