reCaptcha by WebDesignBy: A security weakness
reCaptcha by WebDesignBy is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation. The published affected range is < 2.0.
- Component
- reCaptcha by WebDesignBy
- Plugin slug
recaptcha-by-webdesignby- Affected
- < 2.0
- Safe version
2.0- Published
- Apr 23, 2026
This CVE was published Apr 23, 2026 and is one of 1 known issue for this plugin.
Update, patch or deactivate.
Update reCaptcha by WebDesignBy to 2.0 or later, or disable and remove it until a fixed version is available.
A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.
Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.
Technical description
The reCaptcha by WebDesignBy WordPress plugin before 2.0 does not sanitize or escape the Site Key setting before outputting it in a JavaScript string context via the grecaptcha_js() function. This allows administrators on multisite installations (who do not have the unfiltered_html capability) to inject arbitrary JavaScript that executes for all visitors to the WordPress login page.
CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:U/C:L/I:L/A:N