CVE-2022-0191: The Ad Invalid Click Protector (AICP) WordPress plugin before 1.2.7 does not have CSRF check deleting banned u
CVE-2022-0191 is a medium-severity flaw (CVSS 6.5) affecting ad invalid click protector. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
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
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 6.5 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.6% (top 52%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2022-05-02 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-0191?
ad invalid click protector: upgrade to 1.2.7. Exact commands for each OS are on this page.
Is CVE-2022-0191 being exploited?
CVE-2022-0191 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-0191 affect?
CVE-2022-0191 affects ad invalid click protector. Severity is medium (CVSS 6.5). 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
How urgent is CVE-2022-0191?
Priority 40/100. Public exploit reference
Software pages
Related CVEs
- CVE-2022-0190 HIGH 8.8 UPGRADE The Ad Invalid Click Protector (AICP) WordPress plugin before 1.2.6 is affected by a SQL Injection in the id p