CVE-2015-5533

Count per Day <= 3.4 - Cross-Site Request Forgery

2015-07-22 00:00

Strategic Overview

Status: Patched in 3.4.1
Affected Plugin: Count per Day
Affected Version: < 3.4.1
CVSS: 7.2High
Weakness type: CWE-352 · Cross-Site Request Forgery (CSRF)
CVE: CVE-2015-5533

At a glance

CVE-2015-5533 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the Count per Day WordPress plugin, affecting versions < 3.4.1. It carries a CVSS score of 7.2 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). The issue is fixed in version 3.4.1; sites on affected versions should update now. Disclosed July 2015, reported by pvdl.

Vulnerability Overview

SQL injection vulnerability in counter-options.php in the Count Per Day plugin before 3.4.1 for WordPress allows remote authenticated administrators to execute arbitrary SQL commands via the cpd_keep_month parameter to wp-admin/options-general.php. NOTE: this can be leveraged using CSRF to allow remote attackers to execute arbitrary SQL commands.

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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in Count per Day < 3.4.1 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Count per Day the fix is 3.4.1: builds < 3.4.1 are affected, anything from 3.4.1 onward is not.

Remediation

Update to version 3.4.1, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Count per Day: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Count per Day 3.4.1 closes this, and updating the plugin is the step that ends it.

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2015-5533 https://www.wordfence.com/threat-intel/vulnerabilities/id/30eda147-f02a-4b3c-a51c-665aa4c75c93 https://nvd.nist.gov/vuln/detail/CVE-2015-5533

Related records

Other vulnerabilities in Count per Day

CVSS Vector

7.2

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredHigh
User InteractionNone
ScopeUnchanged
ConfidentialityHigh
IntegrityHigh
AvailabilityHigh

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/