CVE-2015-10001

WP-Stats < 2.52 - Cross-Site Request Forgery

2015-06-17 00:00
Anonymous

Strategic Overview

Status
Patched in 2.52
Affected Plugin
WP-Stats
Affected Version
< 2.52
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2015-10001
View all WP-Stats vulnerabilities

At a glance

CVE-2015-10001 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP-Stats WordPress plugin, affecting versions < 2.52. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.52; sites on affected versions should update now. Disclosed June 2015.

Vulnerability Overview

The WP-Stats WordPress plugin before 2.52 does not have CSRF check in admin-menu when saving its settings, and did not escape some of them when outputting them, allowing attacker to make logged in high privilege users change them and set Cross-Site Scripting payloads in wordpress-admin-panel.

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.

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

Reaching this weakness in WP-Stats < 2.52 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 WP-Stats the fix is 2.52: builds < 2.52 are affected, anything from 2.52 onward is not.

Remediation

Update to version 2.52, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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