CVE-2025-30862

reCAPTCHA for all <= 2.22 - Cross-Site Request Forgery

2025-03-27 00:00
Skalucy

Strategic Overview

Status
Patched in 2.23
Affected Version
<= 2.22
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2025-30862
View all Integrator for Turnstile and reCAPTCHA. vulnerabilities

At a glance

CVE-2025-30862 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Integrator for Turnstile and reCAPTCHA. WordPress plugin, affecting versions <= 2.22. 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.23; sites on affected versions should update now. Disclosed March 2025, reported by Skalucy.

Vulnerability Overview

The Cloudflare Turnstile or reCAPTCHA For any Pages, to Block Spam and Hackers Attack. plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 2.22. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to perform an unauthorized action 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 Integrator for Turnstile and reCAPTCHA. <= 2.22 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 Integrator for Turnstile and reCAPTCHA. the fix is 2.23: builds <= 2.22 are affected, anything from 2.23 onward is not.

Remediation

Update to version 2.23, or a newer patched version

How does WordSec protect against this?

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