Count Per Day Vulnerabilities
The Count Per Day WordPress plugin has 4 known security vulnerabilities, including 1 critical. The most recent was disclosed on August 5, 2016. Check whether your site runs an affected version below.
View Count Per Day on WordPress.orgSummary
Latest vulnerability disclosed on August 5, 2016.
Recommendation
WPSentry recommends extreme caution
Only run Count Per Day if it is updated to the latest patched release. This plugin has a history of 1 critical, potentially exploitable vulnerability. If you already use it, update immediately — or consider a safer alternative.
Is your site affected?
Run a free external scan to detect Count Per Day and 35+ other WordPress security checks — no login or plugin required.
Known Count Per Day vulnerabilities
- high
Count per Day < 3.5.5 - Unauthenticated Stored Cross-Site Scripting
Affected versions: <3.5.5Disclosed August 5, 2016 - high
Count per Day < 3.5.5 - Reflected Cross-Site Scripting
Affected versions: <3.5.5Disclosed August 4, 2016 - critical
Count Per Day <= 3.2.3 - Path Disclosure and Denial of Service
Affected versions: <=3.2.3Disclosed August 1, 2014 - high
Count per Day < 3.2.6 - Reflected Cross-Site Scripting
Affected versions: <3.2.6Disclosed August 1, 2014
How to stay protected
Update promptly
Keep Count Per Day on its latest release — most vulnerabilities are fixed in newer versions.
Scan regularly
Run an external scan after every update to catch outdated or vulnerable software early.
Monitor continuously
Enable monitoring to get alerted the moment a new issue affects your stack.