Ad Invalid Click Protector (AICP) <= 1.2.5.2 - Reflected Cross-Site Scripting and Cross-Site Request Forgery

2022-04-05 00:00
Unknown

Strategic Overview

Status
Patched in 1.2.7
Affected Version
<= 1.2.5.2
CVSS
6.1Medium
Weakness type
CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE
CVE pending
View all Ad Invalid Click Protector (AICP) vulnerabilities

At a glance

This record tracks a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the Ad Invalid Click Protector (AICP) WordPress plugin, affecting versions <= 1.2.5.2. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.2.7; sites on affected versions should update now. Disclosed April 2022, reported by Unknown.

Vulnerability Overview

The Ad Invalid Click Protector (AICP) WordPress plugin is vulnerable to Reflected Cross-Site Scripting via the page parameter and Cross-Site Request Forgery that allows attackers to delete banned users.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in Ad Invalid Click Protector (AICP) <= 1.2.5.2 takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For Ad Invalid Click Protector (AICP) the fix is 1.2.7: builds <= 1.2.5.2 are affected, anything from 1.2.7 onward is not.

Remediation

Update to version 1.2.7, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Ad Invalid Click Protector (AICP): WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Ad Invalid Click Protector (AICP) 1.2.7 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C