Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessRegister or log in as Subscriber
-
DeliveryLoad admin page and scrape wp_localize_script nonce
-
ExploitPOST to admin-ajax.php ajax_run_tool with create_temporary_link for admin user
-
ExecutionReceive passwordless magic-login URL
-
PersistVisit URL to authenticate as Administrator
-
ImpactInstall backdoor plugin or modify site content
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Alternate path authentication
|
| Exploitation Conditions | Requires (1) the WP Captcha PRO or Advanced Google reCAPTCHA plugin installed and active at version 5.38 or earlier, (2) an authenticated WordPress session at Subscriber level or above - trivially obtained on sites with open registration enabled, otherwise requiring credential compromise of any low-privilege account, (3) the plugin's welcome pointer not yet dismissed by an administrator, since that condition gates the wp_localize_script() nonce exposure on non-settings admin pages, and (4) network reach to /wp-admin/admin-ajax.php. No user interaction by a victim is required (UI:N), and the create_temporary_link tool accepts arbitrary target user IDs, so even with PR:L the attacker can pivot to Administrator. The welcome-pointer prerequisite and the registration model are the practical limiters: on sites where an admin has already dismissed the pointer, the nonce will not be exposed via that vector and exploitation through this exact path is blocked. |
| Impact | The CVSS 3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H) accurately reflects real-world risk: exploitation is network-reachable, low-complexity, requires only low-privilege authentication (any Subscriber), needs no user interaction, and yields full confidentiality, integrity, and availability impact through Administrator takeover. WordPress sites that allow open user registration - common for membership, e-commerce, and community sites - effectively reduce the PR:L barrier to PR:N because attackers can self-register a Subscriber account. EPSS and KEV data were not provided in the input, and no public exploit is identified at time of analysis; however, Wordfence has published a threat-intel advisory, and the technical chain (nonce-only check + magic-login tool) is straightforward enough that weaponization by competent researchers is likely once details propagate. Treat as a high priority for any site running this plugin with open registration; medium-high priority elsewhere because any compromised low-privilege account becomes a path to full takeover. |
| Exploit ScenarioDerived | An attacker registers a Subscriber account on a WordPress site (or compromises any existing low-privilege account), logs in, and loads any non-settings admin page where the plugin's welcome pointer is still active, harvesting the AJAX nonce from the wp_localize_script() output. They then POST to admin-ajax.php invoking ajax_run_tool() with the create_temporary_link tool targeting user ID 1 (the typical Administrator), receive a passwordless magic-login URL, and visit it to be authenticated as Administrator with full site control. No public exploit is identified at time of analysis, but the chain is reproducible from the public description. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 05, 2026
Authentication bypass in WP Captcha PRO (and the free Advanced Google reCAPTCHA plugin sharing the same slug) for WordPress versions through 5.38 allows authenticated Subscriber-level users to log in as any account, including Administrator. The flaw chains a missing capability check in the ajax_run_tool() AJAX handler with the create_temporary_link tool that issues passwordless login links for arbitrary users, enabling full account takeover. No public exploit identified at time of analysis and the vulnerability is not listed in CISA KEV.
RemediationAI
Upgrade to a version greater than 5.38 once published by WebFactory; the input data does not name a specific fixed release, so consult the vendor advisory at https://getwpcaptcha.com and the Wordfence entry at https://www.wordfence.com/threat-intel/vulnerabilities/id/8731565f-4d8a-49e6-9c38-6d4f5e51d68c?source=cve for the exact patched version (patch available per vendor advisory; released patched version not independently confirmed from input). Until the patched build is deployed, deactivate the plugin entirely (most reliable mitigation, at the cost of losing CAPTCHA protection on login/comment/registration forms - pair with another CAPTCHA plugin or temporarily disable open registration to compensate), or as a partial workaround disable open user registration in Settings > General (removes the Subscriber-self-enrollment path but does not protect sites with existing low-privilege accounts), and restrict /wp-admin and admin-ajax.php access by IP at the web server or WAF layer where feasible. A virtual patch blocking POST requests to admin-ajax.php with action=run_tool (or the plugin's specific action name) for non-administrator sessions can also be deployed via Wordfence, ModSecurity, or equivalent WAF rules.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The plugin is a WordPress security/CAPTCHA add-on developed by WebFactory (CPE cpe:2.3:a:webfactory:advanced_google_recaptcha), where the premium WP Captcha PRO and the free Advanced Google reCAPTCHA share the same plugin slug and codebase. The root cause is CWE-288 (Authentication Bypass Using an Alternate Path or Channel): the ajax_run_tool() AJAX endpoint enforces only a nonce check via check_ajax_referer() without calling current_user_can() or any role/capability gate. Because WordPress nonces are intended as CSRF tokens - not authorization controls - and the relevant nonce is broadcast to every logged-in user via wp_localize_script() on non-settings admin pages whenever the plugin's welcome pointer has not been dismissed, any authenticated session can invoke privileged tools. One such tool, create_temporary_link, generates passwordless magic-login URLs for arbitrary user IDs, which handle_temporary_links() then accepts and authenticates without further authorization validation.
Know when Advanced Google Recaptcha gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
Primary rating from NVD · only source for this CVE.
CVSS VectorNVD
DescriptionCVE.org
The WP Captcha PRO (the premium version of the Advanced Google reCAPTCHA plugin, both have the same slug) plugin for WordPress is vulnerable to Authentication Bypass in all versions up to, and including, 5.38. This is due to the ajax_run_tool() AJAX handler relying solely on a nonce check (check_ajax_referer) for security without performing any capability check, combined with the create_temporary_link tool allowing the generation of passwordless login links for arbitrary users, and the handle_temporary_links() function authenticating visitors via these links without any additional authorization validation. The required nonce is exposed to all authenticated backend users (including Subscribers) via wp_localize_script() on all non-settings admin pages when the plugin's welcome pointer has not been dismissed. This makes it possible for authenticated attackers, with Subscriber-level access and above, to bypass normal authentication and log in as any user, including Administrators, resulting in complete account takeover.
Executive ViewAI
WP Captcha PRO and the associated Advanced Google reCAPTCHA plugin create a critical account takeover vulnerability affecting WordPress sites through version 5.38. The flaw allows any authenticated user-even those with basic subscriber access-to assume administrator control without requiring passwords. Without a vendor patch currently available, organizations using these plugins face imminent risk of complete administrative compromise and site takeover.
No vendor-released patch identified at time of analysis. Interim mitigations: (1) Immediately disable and remove both plugins; (2) Restrict /wp-admin/ IP access via firewall/WAF; (3) Enforce multi-factor authentication (MFA) for all accounts; (4) Deploy WAF rules blocking AJAX requests to the ajax_run_tool handler; (5) Reduce Subscriber user role permissions to absolute minimum; (6) Implement real-time monitoring of admin account access and modifications.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.
More in Advanced Google Recaptcha
View allRemote code execution in WP Captcha PRO (premium version of the Advanced Google reCAPTCHA WordPress plugin) through vers
The Advanced Google reCaptcha plugin for WordPress is vulnerable to CAPTCHA Bypass in versions up to, and including, 1.2
Unauthenticated attackers can defeat the Google reCAPTCHA verification performed by the Advanced Google reCAPTCHA WordPr
EUVD-2026-34888
GHSA-f32q-xh2j-mm3g
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB