PatchTheCVEcount per day project vulnerabilities
Recent CVEs affecting count per day project products. 3 tracked.
count per day project has 3 tracked vulnerabilities, 0 critical. A fixed release or vendor patch exists for 3. Most recent: 2019-08-21. Highest priority: CVE-2015-5533 (score 54/100).
- CVE-2015-5533 HIGH 7.2 UPGRADE SQL injection vulnerability in counter-options.php in the Count Per Day plugin before 3.4.1 for WordPress allo
- CVE-2013-7472 MEDIUM 6.1 UPGRADE The "Count per Day" plugin before 3.2.6 for WordPress allows XSS via the wp-admin/?page=cpd_metaboxes daytosho
- CVE-2012-6714 MEDIUM 6.1 UPGRADE The count-per-day plugin before 3.2.3 for WordPress has XSS via search words.
FAQ
How do I fix count per day project vulnerabilities?
Open the CVE for your version, check the affected range, then follow the listed action: upgrade to the fixed release, or downgrade or mitigate if no fix exists yet. Commands for each OS are shown on every CVE page.
Is count per day project being exploited right now?
None of the tracked count per day project CVEs are on the CISA Known Exploited Vulnerabilities list at the moment. This is checked every 20 minutes.
Which count per day project CVE should I patch first?
CVE-2015-5533 currently ranks highest (54/100): SQL injection vulnerability in counter-options.php in the Count Per Day plugin before 3.4.1 for WordPress allo.