Count Per Day <= 3.2.3 - Path Disclosure and Denial of Service

2014-08-01 00:00
alej andr0

Strategic Overview

Status
Patched in 3.2.4
Affected Plugin
Count per Day
Affected Version
<= 3.2.3
CVSS
9.1Critical
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE pending
View all Count per Day vulnerabilities

At a glance

This record tracks a critical-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Count per Day WordPress plugin, affecting versions <= 3.2.3. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high confidentiality, availability impact). Exploitation requires no authentication. The issue is fixed in version 3.2.4; sites on affected versions should update now. Disclosed August 2014, reported by alej andr0.

Vulnerability Overview

The Count Per Day plugin for WordPress is vulnerable to Path Disclosure and Denial of Service in versions up to, and including, 3.2.3 via the 'notes.php' file. This makes it possible for unauthenticated attackers to disclose sensitive information and slow/deny the responsiveness of the vulnerable service.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, availability.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

Reaching this weakness in Count per Day <= 3.2.3 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.

The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For Count per Day the fix is 3.2.4: builds <= 3.2.3 are affected, anything from 3.2.4 onward is not.

Remediation

Update to version 3.2.4, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Count per Day 3.2.4 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/7612b680-fb4a-4c5a-aa46-fb3473da78b4

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C