A week ago, the developers of the 200,000+ install WordPress plugin Fluent Forms tried to address a security issue in the plugin, but failed, leaving a vulnerability in the plugin. You wouldn’t know about that from various WordPress plugin vulnerability data providers that claim they have the most comprehensive data (Wordfence) or to be the first to warn about vulnerabilities (WPScan and Patchstack), since they haven’t warned their customers about this yet. You wouldn’t know about that from the changelog for the plugin, since the developer didn’t disclose it. If they had fixed the issue, there would still be a problem, since they didn’t bump the version number when they made the change, so those already on the latest version wouldn’t have gotten the upgrade.
As at least one of our customers is using the plugin, a machine learning (artificial intelligence (AI)) based system we created reviewed the relevant change and flagged it as possibly fixing a vulnerability. We manually reviewed the change and saw that the developer had applied the wrong security change (more on that coming in a separate more technical post about the issue more generally). Saturday, we confirmed that this was an exploitable vulnerability (and not just a security issue), notified the developer of the issue and offered to help them fix it, and warned our customers that the plugin is vulnerable. [Read more]