CAPTCHA 4WP < 7.1.0 - Local File Inclusion via CSRF

published 2022-08-01 4 y ago modified 2026-06-17 4 mo ago also EUVD-2022-34468

cvss: 8.8; version 3.1, NVD
cisa kev: Not listed; not in CISA's catalog
epss: 0.6%; EPSS 0.6% chance of exploitation in 30 days, percentile 48%
public exploits: 0; none known

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.

Patch / fix

fixed in 1

wpwhitesecurity captcha_4wp 7.1.0

Exploit prediction

0.59% chance of exploitation in the next 30 days, higher than 48% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

wpscan.com https://wpscan.com/vulnerability/e777784f-5ba0-4966-be27-e0a0cbbfe056 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by	version	score	vector
NVD	3.1	8.8	CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Affected products

Unknown CAPTCHA 4WP

Classification

Weakness

CWE-22 Improper Limitation of a Pathname to a Restricted Directory
CWE-352 Cross-Site Request Forgery

Technology feeds

WordPress rss critical rss

References

wpscan.com /vulnerability/e777784f-5ba0-4966-be27-e0a0cbbfe056
exploit, third-party-advisory

Sources

CVE List CVE-2022-2184
NVD CVE-2022-2184

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

Summary