CVE-2026-5411 HIGH

CVE-2026-5411: WP Captcha PRO <= 5.38 - Missing Authorization to Authenticated (Subscriber+) Arbitrary File Upload

Vendor Webfactory
Product Advanced Google reCAPTCHA
Weakness CWE-434 · Unrestricted file upload
Published June 5, 2026
Last update June 6, 2026

CVSS base score

8.8/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality High
Integrity High

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

What the vulnerability does

01Description

The WP Captcha PRO (the premium version of the Advanced Google reCAPTCHA plugin, both have the same slug) plugin for WordPress is vulnerable to arbitrary file upload in all versions up to, and including, 5.38. This is due to a capability check in the save_ajax() function of the licensing module, combined with unrestricted file extraction in sync_cloud_protection(). This makes it possible for authenticated attackers, with Subscriber-level access and above, to upload arbitrary files including PHP webshells to the server by injecting a malicious cloud_protection_url into the license meta, which the plugin then downloads and extracts without file type validation into a web-accessible uploads directory. This can be used for remote code execution. Note: The vulnerability can only be exploited with a remote URL if "allow_url_fopen" is enabled in the php.ini config.

Explanation of Vulnerability in Simple Terms

02Summary

Advanced Google reCAPTCHA versions 5.38 and earlier contain an unrestricted file upload vulnerability. An authenticated user with low privileges can upload arbitrary files to the site without proper validation. This can lead to remote code execution, data theft, or site compromise. Update to a version newer than 5.38 immediately.

What an attacker can do

03Attacker Capabilities

Upload arbitrary files to the site and execute code or steal data.

Potential impact on your site

04Site Impact

Attackers with user accounts can upload malicious files and take over your site or access sensitive data.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege authenticated account on the site.

Key dates

06Disclosure timeline

June 5, 2026 CVE published
June 6, 2026 Record updated