WP Crowdfunding <= 2.1.5 - Cross-Site Request Forgery

2023-09-08 00:00
Anonymous

Strategic Overview

Status
Patched in 2.1.6
Affected Plugin
WP Crowdfunding
Affected Version
<= 2.1.5
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE pending
View all WP Crowdfunding vulnerabilities

At a glance

This record tracks a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Crowdfunding WordPress plugin, affecting versions <= 2.1.5. 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.1.6; sites on affected versions should update now. Disclosed September 2023.

Vulnerability Overview

The WP Crowdfunding plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.1.5. This is due to missing or incorrect nonce validation on the settings_reset function. This makes it possible for unauthenticated attackers to reset plugin 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)

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

Remediation

Update to version 2.1.6, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/e4dc8f18-d990-4e41-8bf8-dfa9de4c0f6e

Related records

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