CVE-2022-47172

WooLentor <= 2.6.2 - Cross-Site Request Forgery via process_data

2023-07-05 00:00
Muhammad Daffa

Strategic Overview

Status
Patched in 2.6.3
Affected Plugin
ShopLentor – All-in-One WooCommerce Growth & Store Enhancement Plugin
Affected Version
<= 2.6.2
CVSS
4.3Medium
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2022-47172
View all ShopLentor – All-in-One WooCommerce Growth & Store Enhancement Plugin vulnerabilities

At a glance

CVE-2022-47172 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the ShopLentor WordPress plugin, affecting versions <= 2.6.2. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 2.6.3; sites on affected versions should update now. Disclosed July 2023, reported by Muhammad Daffa.

Vulnerability Overview

The WooLentor plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.6.2. This is due to missing or incorrect nonce validation on the process_data function. This makes it possible for unauthenticated attackers to change plugin settings via a 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.

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

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

Remediation

Update to version 2.6.3, or a newer patched version

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-47172https://www.wordfence.com/threat-intel/vulnerabilities/id/5c068079-0857-4116-8edb-1bc2fea3c6b7https://nvd.nist.gov/vuln/detail/CVE-2022-47172

Related records

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