CVE-2024-2946 MEDIUM

CVE-2024-2946: ShopLentor – WooCommerce Builder for Elementor & Gutenberg +12 Modules – All in One Solution (formerly WooLentor) <= 2.8.4 - Authenticated (Contributor+) Stored Cross-site Scripting via QR Code Widget

Vendor Devitemsllc
Product ShopLentor – All-in-One WooCommerce Growth & Store Enhancement Plugin
Weakness CWE-79 · XSS
Published April 9, 2024
Last update April 8, 2026

CVSS base score

6.4/10
Attack vector Network
Attack complexity Low
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

What the vulnerability does

01Description

The ShopLentor – WooCommerce Builder for Elementor & Gutenberg +12 Modules – All in One Solution (formerly WooLentor) plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's QR Code Widget in all versions up to, and including, 2.8.4 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Explanation of Vulnerability in Simple Terms

02Summary

ShopLentor versions up to 2.8.4 contain a stored cross-site scripting (XSS) vulnerability that allows authenticated users with low privileges to inject malicious scripts. The vulnerability has changed scope, meaning injected code can affect other users and site functionality. An attacker needs a valid user account to exploit this flaw.

What an attacker can do

03Attacker Capabilities

Inject malicious JavaScript that executes in other users' browsers and affects site functionality.

Potential impact on your site

04Site Impact

Authenticated attackers can deface pages, steal session data, or redirect users to malicious sites.

Conditions required to exploit

05Prerequisites

Attacker must have a low-privilege user account on the site; no user interaction required.

Key dates

06Disclosure timeline

April 9, 2024 CVE published
April 8, 2026 Record updated

Related vulnerabilities

08Related CVE