CVE-2026-5415
Authentication Bypass in WP Captcha PRO WordPress Plugin
Publication date: 2026-06-05
Last updated on: 2026-06-05
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| wp_captcha_pro | wp_captcha_pro | to 5.38 (inc) |
| webfactory_ltd | wp_captcha_pro | to 5.38 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-288 | The product requires authentication, but the product has an alternate path or channel that does not require authentication. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
The WP Captcha PRO plugin for WordPress has an authentication bypass vulnerability in all versions up to and including 5.38. This occurs because the ajax_run_tool() AJAX handler only checks a nonce for security without verifying user capabilities. Additionally, the create_temporary_link tool can generate passwordless login links for any user, and the handle_temporary_links() function authenticates users via these links without further authorization checks. The nonce required for this process is exposed to all authenticated backend users, including those with Subscriber-level access, making it possible for such users to bypass normal authentication and log in as any user, including administrators.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability in WP Captcha PRO allows authenticated attackers with Subscriber-level access to bypass normal authentication and log in as any user, including Administrators, resulting in complete account takeover.
Such an account takeover can lead to unauthorized access to sensitive personal data or protected health information, which may violate data protection regulations such as GDPR and HIPAA.
Therefore, this vulnerability poses a significant risk to compliance with these standards by potentially enabling data breaches and unauthorized data access.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability involves the WP Captcha PRO WordPress plugin versions up to and including 5.38, where an authentication bypass can occur due to insecure AJAX handlers and exposed nonces.
To detect if your system is vulnerable, first verify if the WP Captcha PRO plugin is installed and its version is 5.38 or below.
You can check the plugin version on your WordPress site by running the following command in the WordPress root directory:
- wp plugin list | grep wp-captcha-pro
Alternatively, you can inspect the plugin files or the WordPress admin dashboard to confirm the version.
To detect exploitation attempts or suspicious AJAX requests related to this vulnerability, monitor HTTP requests to the AJAX handler endpoint that uses the ajax_run_tool() function.
For example, you can use network monitoring tools or web server logs to look for POST requests to admin-ajax.php with parameters indicating the use of create_temporary_link or handle_temporary_links.
A sample command to search web server logs for such requests might be:
- grep 'admin-ajax.php' /var/log/apache2/access.log | grep 'create_temporary_link'
- grep 'admin-ajax.php' /var/log/apache2/access.log | grep 'handle_temporary_links'
Additionally, monitoring for unexpected logins or account takeovers, especially for administrator accounts, can help detect exploitation.
How can this vulnerability impact me? :
This vulnerability allows attackers with low-level authenticated access (Subscriber or higher) to bypass normal authentication mechanisms and log in as any user, including administrators. This can lead to complete account takeover, allowing the attacker full control over the WordPress site, potentially resulting in data theft, site defacement, or further exploitation.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, immediately update the WP Captcha PRO plugin to a version later than 5.38 where the authentication bypass issue is fixed.
Additionally, restrict access to authenticated backend users with Subscriber-level access or higher until the update is applied, as the vulnerability allows such users to bypass authentication and take over accounts.
Consider disabling or removing the plugin temporarily if an update is not immediately available or feasible.