Count per Day
count-per-day · plugin
Known security vulnerabilities for Count per Day. Find out in seconds which version runs on your site with WP Lens.
6 known vulnerabilities
2 exploitable without logging in · 3 with public exploit code · latest Aug 21, 2019
Closed on wordpress.org
Removed from the directory on Oct 27, 2019 · reason: guideline violation. A closed component gets no more updates; installed copies keep running and their vulnerabilities stay open. Remove it or replace it with a maintained alternative.
wordpress.org status checked on Oct 2, 2026
Vulnerabilities
- High 7.2
CVE-2015-5533high privilege
SQL injection vulnerability in counter-options.php in the Count Per Day plugin before 3.4.1 for WordPress allows remote authenticated admini
- Medium 6.1
CVE-2012-6714unauthenticated · needs a click
The count-per-day plugin before 3.2.3 for WordPress has XSS via search words.
- Medium 6.1
CVE-2013-7472unauthenticated · needs a click
The "Count per Day" plugin before 3.2.6 for WordPress allows XSS via the wp-admin/?page=cpd_metaboxes daytoshow parameter.
- Medium 5.0
Absolute path traversal vulnerability in download.php in the Count Per Day module before 3.1.1 for WordPress allows remote attackers to read
- Medium 4.3
Multiple cross-site scripting (XSS) vulnerabilities in userperspan.php in the Count Per Day module before 3.2 for WordPress allow remote att
- Medium 4.3
Cross-site scripting (XSS) vulnerability in map/map.php in the Count Per Day module before 3.1.1 for WordPress allows remote attackers to in
The access label is read from the record's own text (e.g. “subscriber+”: subscriber and above). When the text names no role, CVSS decides between “login required” and “high privilege”; no role name is invented. “Needs a click”: the attack depends on a logged-in user following a link (CSRF, reflected XSS).