CVE-2013-10025

WordPress Exit Strategy <= 1.55 - Cross-Site Request Forgery

2013-05-28 00:00
Anonymous

Strategic Overview

Status
Patched in 1.59
Affected Version
<= 1.55
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2013-10025
View all WordPress Exit Strategy vulnerabilities

At a glance

CVE-2013-10025 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WordPress Exit Strategy WordPress plugin, affecting versions <= 1.55. 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 1.59; sites on affected versions should update now. Disclosed May 2013.

Vulnerability Overview

The exit-strategy plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.55. This is due to missing or incorrect nonce validation on the exit_page_admin() function. This makes it possible for unauthenticated attackers to modify the plugin's settings via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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)

WordPress Exit Strategy <= 1.55 carries this weakness at exit_page_admin(), and reaching it 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 WordPress Exit Strategy the fix is 1.59: builds <= 1.55 are affected, anything from 1.59 onward is not.

Remediation

Update to version 1.59, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WordPress Exit Strategy: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WordPress Exit Strategy 1.59 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