3 Sep 2024

Plugin Security Scorecard August Results

August was the first full month our Plugin Security Scorecard was available. A fair amount of plugins were checked. A total of 144 plugins were checked last month. With 35 of those plugins being security plugins.

As can be seen below, the results for security plugins were not good. With 24 of the 35 plugins getting a D+ or below. That comes from a combination of different issues. Some of those plugins have security issues, including vulnerabilities. Some come from developers that have had repeated issues with vulnerabilities and are not addressing the underlying problems. Most security plugins are failing to implement best practices for security, even when they are running into the problems those cause. Then there is the issue of the plugin developers making security claims that are at least not supported with evidence (and often couldn’t be supported with evidence, since they are not true).

The overall results were better than those for just security plugins, but not great. No plugins got an A+ or an A this month. Those grades require the developer is taking proactive measures with security. 55 of the plugins did get a B+ or B, which requires that they are avoiding unnecessary security issues.

The ability to get an A+ or an A gets harder this month, as we now are grading on if the developer is providing a software bill of materials (SBOM) to their plugin. The importance of providing the information included in a SBOM is highlighted with by a plugin with 600,000+ installs failing to update a known vulnerable library included in the plugins for 17 months. Widespread usage of SBOMs would make it easier to catch usage of known vulnerable libraries.

During August we made quite a few improvements to the tool and expanded what it checked. The biggest addition was checking if the results of security review of the plugin are being listed in a security file in the plugin. A good security is the best way to assess the security of a plugin. Before adding that check, we did review of all our own plugins that are actively being developed, which led to security improvements being made to one of them. We also added a warning if results of a security review from a provider that is pretending to do reviews is linked to.

Until SBOMs become widespread, tools checking for known vulnerable libraries can fill some of the gap. So last month we also added a check for security vulnerabilities in a couple of libraries used in WordPress plugins. One of them that hasn’t been fixed. That one is in multiple fairly popular security plugins, where the developers appear to not be vetting third-party software they are incorporating. And we added a check for usage of WordPress function that is known to be insecure and apparently isn’t intended to be used directly in plugins.

August Security Scorecard Grades for  Security Plugins

August Security Scorecard Grades for Other Plugins

Leave a Reply

Your email address will not be published.