Skip to main content
VulnerabilityPublished

CVE-2026-5411: Advanced Google reCAPTCHA (WordPress plugin) · Unrestricted File Upload

Affects Advanced Google reCAPTCHA (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 8.8 High.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
8.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: evidence found.

    Public exploit code: GitHub proofs of concept

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), GitHub proofs of concept, the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
webfactoryAdvanced Google reCAPTCHAAffected
  • <=5.38
Fixed in–

AI-suggested

Users should check the vendor advisory for updates. Until a fix is available, consider disabling allow_url_fopen in php.ini to prevent remote URL exploitation. Restricting plugin access to trusted users and monitoring for suspicious uploads may reduce risk. Avoid using versions up to and including 5.38 where possible.

Description

The WP Captcha PRO plugin (premium version of Advanced Google reCAPTCHA) for WordPress has a vulnerability allowing authenticated users with Subscriber-level access or higher to upload arbitrary files, including PHP webshells. This occurs due to insufficient file type validation during a file extraction process triggered by a malicious URL in the license meta. Exploitation requires the PHP configuration option allow_url_fopen to be enabled. Versions up to and including 5.38 are affected. This vulnerability can lead to remote code execution on the server.

References

Community reviews

Loading reviews…