CAPTCHA 4WP <= 7.0.6.1 - Cross-Site Request Forgery to Local File Inclusion
Strategic Overview
- Status
- Patched in 7.1.0
- Affected Plugin
- CAPTCHA 4WP – Antispam CAPTCHA solution for WordPress
- Affected Version
<= 7.0.6.1- CVSS
- 8.8High
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2022-2184
At a glance
CVE-2022-2184 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the CAPTCHA 4WP WordPress plugin, affecting versions <= 7.0.6.1. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 7.1.0; sites on affected versions should update now. Disclosed June 2022, reported by ZhongFu Su.
Vulnerability Overview
The CAPTCHA 4WP plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 7.0.6.1. This makes it possible for unauthenticated attackers to inject malicious code, resulting in remote code execution, via forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in CAPTCHA 4WP <= 7.0.6.1 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For CAPTCHA 4WP the fix is 7.1.0: builds <= 7.0.6.1 are affected, anything from 7.1.0 onward is not.
Remediation
Update to version 7.1.0, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to CAPTCHA 4WP: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: CAPTCHA 4WP 7.1.0 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in CAPTCHA 4WP – Antispam CAPTCHA solution for WordPress
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C