To provide a better service for our customers, we have started working to make sure we are providing more complete data on vulnerabilities in WordPress plugins used by our customers. That led to us reviewing a report of a vulnerability in NotificationX that we had not looked at before. We found that the claimed vulnerability didn’t really exist, as it involved a broken security check, which didn’t look to have been needed in the first place. After noticing that, we checked to see if there might be functionality where there were not needed security checks being done were they were needed and we found an instance of that. We found one, though it had been resolved by now, because of a major rewrite of the plugin, which replaced the functionality.

...

---

This post provides insights on a vulnerability in the WordPress plugin NotificationX not discovered by us, where the discoverer hadn't provided the details needed for us to confirm the vulnerability while we were adding it to the data set for our service, so the rest of its contents are limited to subscribers of our service.

If you were using our service, you would have already been warned about this vulnerability if your website is vulnerable due to it. You can try out our service for free and then see the rest of the details of the vulnerability.

For existing customers, please log in to your account to view the rest of the contents of the post.