CVE-2024-1719

Easy PayPal & Stripe Buy Now Button <= 1.8.3 & Contact Form 7 – PayPal & Stripe Add-on <= 2.1 - Cross-Site Request Forgery to Settings Update

2024-02-27 00:00
Krzysztof Zając

Strategic Overview

Status
Patched in 2.2
Affected Plugin
Contact Form 7 – PayPal & Stripe Add-on
Affected Version
<= 2.1
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2024-1719
View all Contact Form 7 – PayPal & Stripe Add-on vulnerabilities

At a glance

CVE-2024-1719 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Contact Form 7 WordPress plugin, affecting versions <= 2.1. 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.2; sites on affected versions should update now. Disclosed February 2024, reported by Krzysztof Zając.

Vulnerability Overview

The Easy PayPal & Stripe Buy Now Button plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.8.3 and in Contact Form 7 – PayPal & Stripe Add-on all versions up to, and including 2.1. This is due to missing or incorrect nonce validation on the 'wpecpp_stripe_connect_completion' function. This makes it possible for unauthenticated attackers to modify the plugins settings and chance the stripe connection 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)

Contact Form 7 <= 2.1 carries this weakness at wpecpp_stripe_connect_completion, 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 Contact Form 7 the fix is 2.2: builds <= 2.1 are affected, anything from 2.2 onward is not.

Remediation

Update to version 2.2, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2024-1719https://www.wordfence.com/threat-intel/vulnerabilities/id/a5276227-9bd4-4ad8-a6b7-ac7d05e8b056https://nvd.nist.gov/vuln/detail/CVE-2024-1719

Related records

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