Count per Day vulnerabilities

Plugin slug count-per-day · 10 known vulnerabilities · latest disclosed 2016-08-05 · WordPress.org page

Every listed vulnerability has a fix. Version 3.5.5 or later is not affected by any of them. If your site runs an older version, update it.

6 of 10 rated high or critical (CVSS 7 or more).

Known vulnerabilities in Count per Day

SeverityAffected versionsFixed inCVEPublishedDetails
High 8.3< 3.5.53.5.5none2016-08-05Advisory
High 7.1< 3.5.53.5.5none2016-08-04Advisory
High 7.2< 3.4.13.4.1CVE-2015-55332015-07-22Advisory
Medium 6.1<= 3.13.1.1CVE-2012-08952014-08-01Advisory
High 7.1< 3.2.63.2.6none2014-08-01Advisory
Critical 9.1<= 3.2.33.2.4none2014-08-01Advisory
Medium 6.1<= 3.1.13.2CVE-2012-34342014-08-01Advisory
Medium 6.1< 3.2.63.2.6CVE-2013-74722013-03-05Advisory
Medium 6.1< 3.2.33.2.3CVE-2012-67142012-07-20Advisory
High 7.5<= 3.13.1.1CVE-2012-08962012-01-12Advisory

Check if a site is affected

Enter a site address to see which version of Count per Day and other plugins it runs, and whether they match a known vulnerability.

Questions

Is the Count per Day plugin safe to use?

All 10 known issues are fixed in current versions (3.5.5 or later). Keeping it updated is what matters.

How do I check which version of Count per Day my site runs?

In WordPress go to Plugins > Installed Plugins. From the outside, the free PluginPeek scan below reads the version from the site's public files.

How do I fix a vulnerable plugin?

Make a full backup, then update it from Dashboard > Updates and check the site afterwards. If you would rather not, we can do it for a fixed $99, paid after you have checked the site.

Check any WordPress site in one click while you browse: Add PluginPeek to Chrome