From time to time a vulnerability is fixed in a plugin without the discoverer putting out a report on the vulnerability and we will put out a post detailing the vulnerability so that we can provide our customers with more complete information on the vulnerability.
One of the areas where we think that the wordpress.org Plugin Directory could probably improve how they handle things is ...
To read the rest of this post you need to have an active account with our service.
For existing customers, please log in to your account to view the rest of the post.
If you are not currently a customer, when you sign up now you can try the service for half off (there are a lot of other reason that you will want to sign up beyond access to posts like this one).
If you are a WordPress plugin security researcher please contact us to get free access to all of our Vulnerability Details posts.