CVE-2022-4745

WP Customer Area <= 8.1.3 - Cross-Site Request Forgery

2023-01-17 00:00
rezaduty

Strategic Overview

Status
Patched in 8.1.4
Affected Plugin
WP Customer Area
Affected Version
<= 8.1.3
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-4745
View all WP Customer Area vulnerabilities

At a glance

CVE-2022-4745 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Customer Area WordPress plugin, affecting versions <= 8.1.3. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 8.1.4; sites on affected versions should update now. Disclosed January 2023, reported by rezaduty.

Vulnerability Overview

The WP Customer Area plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 8.1.3. This is due to missing or incorrect nonce validation on several functions related to file and folder management. This makes it possible for unauthenticated attackers to invoke those functions via forged request granted they can trick a site administrator into performing an action such as clicking on a link.

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. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in WP Customer Area <= 8.1.3 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WP Customer Area the fix is 8.1.4: builds <= 8.1.3 are affected, anything from 8.1.4 onward is not.

Remediation

Update to version 8.1.4, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP Customer Area: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Customer Area 8.1.4 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