CVE-2022-46798

ShopLentor <= 2.5.1 - Cross-Site Request Forgery to Post Updates

2023-02-06 00:00
Muhammad Daffa

Strategic Overview

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

At a glance

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

Vulnerability Overview

The ShopLentor plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 2.5.1. This is due to missing or incorrect nonce validation on the 'templates_ajax_request' function. This makes it possible for unauthenticated attackers to update post metadata such as titles and id numbers 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)

ShopLentor <= 2.5.1 carries this weakness at templates_ajax_request, and reaching it 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.5.2: builds <= 2.5.1 are affected, anything from 2.5.2 onward is not.

Remediation

Update to version 2.5.2, 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.5.2 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2022-46798https://www.wordfence.com/threat-intel/vulnerabilities/id/db952443-2588-4da0-87d8-5bd2d3be039chttps://nvd.nist.gov/vuln/detail/CVE-2022-46798

Related records

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