21 Mar

Hiding That the Head of the WordPress Plugin Directory Mika Epstein Isn’t Making Much Sense Doesn’t Seem Like Proper Forum Moderation

When it comes to fixing the problems with the handling of the security of WordPress plugins we feel that fixing the moderation of the Support Forum is important since right now the moderation of that is used to cover problems up (it doesn’t seems like that is necessarily all that intentional, but it ends up having that effect anyway). One of the problems being covered up is that people in charge of the Plugin Directory really don’t seem up to the task and seem to be unable to work with others to try improve. As example of that take something from a few days ago that was posted on the Support Forum, but isn’t accessible, but we saw because of an email alert we have related to keeping track of discussions that might relate to plugin vulnerabilities.

[Read more]

17 Dec

WordPress Plugin Directory Team Close Plugin Due to Fake Vulnerability Report

When it comes to inappropriate behavior of the moderators of the WordPress Support forum that has lead to us full disclosing vulnerabilities in protest until WordPress gets that situation cleaned up, that inappropriate behavior often has the impact of covering up problems created by those on the WordPress side of things. Whether they are intending to do that to cover up things or not isn’t clear, but the person that appears to be in charge of the moderation, Samuel “Otto” Wood, wears a number of other hats when it comes to WordPress, so there are obvious potential conflict of interest issues. One of the hats he wears is being a member of the six member team running the Plugin Directory, which screwed up in fairly obvious way a few days ago involving plugin CSS & JavaScript Toolbox and then a moderator shut down the possibility of pointing that out.

[Read more]

01 Nov

The Head of the Plugin Directory Mika Epstein Seems Like the One Acting Stupidly Here

When it comes to improving the security of WordPress plugins the two things that stand out that are of most need and have been for years, are warning people when they are using vulnerable plugins and for serious vulnerabilities, which are likely to be exploited, putting out fixes if the developer doesn’t. The reason that hasn’t happened isn’t because of say a lack of resources, before we suspended doing it last year due to continued bad behavior by people on the WordPress side of things, we were to a large degree single handedly making sure that plugins in the Plugin Directory with public disclosed unfixed vulnerabilities didn’t remain in it (when we stopped they started piling up in it). We easily could provide fixes for the vulnerabilities that are likely to be exploited as well. Instead, the reason for the lack of doing those things is that the people on the WordPress side, for reasons that don’t make sense, are blocking those things from happening.

[Read more]