CVE-2022-4938

WCFM Frontend Manager <= 6.5.13 - Cross-Site Request Forgery

2023-04-05 00:00
Chloe Chamberland

Strategic Overview

Status
Patched in 6.6.0
Affected Plugin
WCFM – Frontend Manager for WooCommerce
Affected Version
<= 6.5.13
CVSS
6.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-4938
View all WCFM – Frontend Manager for WooCommerce vulnerabilities

At a glance

CVE-2022-4938 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WCFM WordPress plugin, affecting versions <= 6.5.13. It carries a CVSS score of 6.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 6.6.0; sites on affected versions should update now. Disclosed April 2023, reported by Chloe Chamberland.

Vulnerability Overview

The WCFM Frontend Manager plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 6.6.0 due to missing nonce checks on various AJAX actions. This makes it possible for unauthenticated attackers to perform a wide variety of actions such as modifying knowledge bases, modifying notices, modifying payments, managing vendors, capabilities, and so much more, via a forged request granted they can trick a site's administrator into performing an action such as clicking on a link. There were hundreds of AJAX endpoints affected.

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-352: Cross-Site Request Forgery (CSRF)

Reaching this weakness in WCFM <= 6.5.13 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 WCFM the fix is 6.6.0: builds <= 6.5.13 are affected, anything from 6.6.0 onward is not.

Remediation

Update to version 6.6.0, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WCFM: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WCFM 6.6.0 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-4938https://www.wordfence.com/threat-intel/vulnerabilities/id/798b57ad-0922-435c-8b4d-8a96b388b314https://nvd.nist.gov/vuln/detail/CVE-2022-4938

Related records

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