CVE-2023-32599

reCAPTCHA for all <= 1.22 - Missing Authorization via recaptcha_for_all_image_select

2023-05-15 00:00
Jonas Höbenreich

Strategic Overview

Status
Patched in 1.23
Affected Version
<= 1.22
CVSS
4.3Medium
Weakness type
CWE-862 · Missing Authorization
CVE
CVE-2023-32599
View all Integrator for Turnstile and reCAPTCHA. vulnerabilities

At a glance

CVE-2023-32599 is a medium-severity Missing Authorization vulnerability in the Integrator for Turnstile and reCAPTCHA. WordPress plugin, affecting versions <= 1.22. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). The root cause is a missing authorization check on a reachable function. The issue is fixed in version 1.23; sites on affected versions should update now. Disclosed May 2023, reported by Jonas Höbenreich.

Vulnerability Overview

The reCAPTCHA for all plugin for WordPress is vulnerable to unauthorized plugin settings update due to a missing capability check on the recaptcha_for_all_image_select function in versions up to, and including, 1.22. This makes it possible for authenticated attackers , with subscriber-level access and above, to change plugin settings.

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 interaction from a victim user.

CWE-862: Missing Authorization

Reaching this weakness in Integrator for Turnstile and reCAPTCHA. <= 1.22 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.

Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Integrator for Turnstile and reCAPTCHA. the fix is 1.23: builds <= 1.22 are affected, anything from 1.23 onward is not.

Remediation

Update to version 1.23, or a newer patched version

How does WordSec protect against this?

Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Integrator for Turnstile and reCAPTCHA. 1.23 closes this, and updating the plugin is the step that ends it.

  • Login Security
  • Alerts

External References

Related records

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