WordPress security changelog
HIGH CVE-2022-2184 Modified

CAPTCHA 4WP: Cross-site request forgery

CAPTCHA 4WP is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.

CVE / CNA score 8.8 CVSS · contact@wpscan.com
NVD score 8.8 CVSS 3.1 · nvd@nist.gov
Component
CAPTCHA 4WP
Plugin slug
captcha-4wp
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Aug 01, 2022
Weakness
CWE-22 — Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
CWE-352 — Cross-Site Request Forgery (CSRF)

This CVE was published Aug 01, 2022 and is one of 1 known issue for this plugin.

Update, patch or deactivate.

Update CAPTCHA 4WP to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

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 CAPTCHA 4WP WordPress plugin before 7.1.0 lets user input reach a sensitive require_once call in one of its admin-side templates. This can be abused by attackers, via a Cross-Site Request Forgery attack to run arbitrary code on the server.

NVD vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Primary and upstream sources