Strategic Overview
- Status
- Unpatched
- Affected Plugin
- Conditional CAPTCHA
- Affected Version
<= 4.0.0- CVSS
- 5.3Medium
- Weakness type
- CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
- CVE
CVE-2026-1369
At a glance
CVE-2026-1369 is a medium-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the Conditional CAPTCHA WordPress plugin, affecting versions <= 4.0.0. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed January 2026, reported by Bob Matyas.
Vulnerability Overview
The Conditional CAPTCHA plugin for WordPress is vulnerable to Open Redirect in all versions up to, and including, 4.0.0. This is due to insufficient validation on the redirect url supplied via a parameter. This makes it possible for unauthenticated attackers to redirect users to potentially malicious sites if they can successfully trick them into performing an action.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-601: URL Redirection to Untrusted Site ('Open Redirect')
Reaching this weakness in Conditional CAPTCHA <= 4.0.0 takes no account at all. An open redirect is a page that takes a destination from the request and sends the browser there without checking that the destination belongs to the site.
A link that starts on a trusted domain finishes on an attacker's, which is what makes phishing and consent-screen abuse credible to the person clicking it. No fixed build of this plugin is recorded for Conditional CAPTCHA yet, so installs running <= 4.0.0 stay exposed until the vendor ships one.
Remediation
No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.
How does WordSec protect against this?
Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.
- Firewall
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C