EUVD-2026-38669
GHSA-r3xp-pqgc-3wvf
Severity by source
AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
PR:N because attacker needs no site credentials; A:L added over provided vector because plugin uninstall and log deletion constitute partial availability loss of the plugin's security and audit functions.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N
Lifecycle Timeline
2DescriptionCVE.org
The Blue Captcha plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to and including 2.0.1. This is due to missing or incorrect nonce validation on the main admin panel (blcap_main_page) and on the Hall of Shame and Log subpages, which accept a 'blcap_action' / 'action' parameter from $_REQUEST and perform destructive operations (plugin uninstall via blcap_uninstall(), log deletion via blcap_delete_logs(), Hall of Shame deletion via blcap_delete_ip_db(), and adding IPs to the banned list via update_option('blcap_settings')) with no wp_verify_nonce(), check_admin_referer(), or check_ajax_referer() calls anywhere in the codebase. This makes it possible for unauthenticated attackers to uninstall the plugin, delete audit logs, remove Hall of Shame entries, and add arbitrary IP addresses to the block list via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
AnalysisAI
Cross-Site Request Forgery in the Blue Captcha WordPress plugin (versions ≤ 2.0.1) allows unauthenticated attackers to trigger destructive administrative operations - including plugin uninstall, audit log deletion, Hall of Shame wipe, and arbitrary IP blocklist manipulation - by tricking a logged-in administrator into clicking a crafted link. The root cause is a complete absence of nonce validation (wp_verify_nonce, check_admin_referer, check_ajax_referer) across all admin handler entry points, confirmed by Wordfence with direct source code references. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | The attacker must socially engineer a currently authenticated WordPress administrator into visiting a malicious page or clicking a crafted link while their browser session on the target site is active - this is the critical limiting condition (CVSS UI:R). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 base score of 4.3 (Medium) is driven by AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:L/A:N. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker identifies a WordPress site running Blue Captcha ≤ 2.0.1, then crafts a webpage containing a hidden image or auto-submitting form that issues a GET or POST request to the target site's wp-admin URL with the parameter `blcap_action=uninstall`. The attacker sends the page link to the site administrator via phishing email or an embedded link in a comment notification; when the administrator opens the link while their WordPress session cookie is active, the browser transparently sends the forged request and the plugin is uninstalled - simultaneously removing CAPTCHA protection from the site and, if a follow-up log-deletion request is chained, destroying any audit evidence. … |
| Remediation | No vendor-released patch has been identified at time of analysis; the fix version is unknown and not stated in the Wordfence advisory or any other available reference. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
Same weakness CWE-352 – Cross-Site Request Forgery (CSRF)
View allShare
External POC / Exploit Code
Leaving vuln.today