ShopLentor <= 2.9.8 - Authenticated (Contributor+) Sensitive Information Exposure via WL: FAQ Widget Elementor Template
Strategic Overview
- Status
- Patched in 2.9.9
- Affected Version
<= 2.9.8- CVSS
- 4.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE-2024-9538
At a glance
CVE-2024-9538 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the ShopLentor WordPress plugin, affecting versions <= 2.9.8. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires an authenticated account at Contributor level or above. The issue is fixed in version 2.9.9; sites on affected versions should update now. Disclosed October 2024, reported by Ankit Patel.
Vulnerability Overview
The ShopLentor plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.9.8 via the 'render' function in includes/addons/wl_faq.php. This makes it possible for authenticated attackers, with Contributor-level access and above, to extract sensitive private, pending, and draft Elementor template data.
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 interaction from a victim user.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
ShopLentor <= 2.9.8 carries this weakness at render, and reaching it takes an account at Contributor level or above. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. For ShopLentor the fix is 2.9.9: builds <= 2.9.8 are affected, anything from 2.9.9 onward is not.
Remediation
Update to version 2.9.9, or a newer patched version
How does WordSec protect against this?
The fix is the thing that ends this: ShopLentor 2.9.9 closes this, and updating the plugin is the step that ends it.
- Alerts
External References
Related records
Other vulnerabilities in ShopLentor – All-in-One WooCommerce Growth & Store Enhancement Plugin
- 9.8CVE-2025-12493: ShopLentor <= 3.2.5 Local PHP File Inclusion
CVE-2025-12493 - 9.8CVE-2023-0232: WooLentor <= 2.5.3 PHP Object Injection
CVE-2023-0232 - 8.6CVE-2026-1714: ShopLentor <= 3.3.2 Email Relay Abuse
CVE-2026-1714 - 7.2CVE-2026-6020: ShopLentor <= 3.3.7 Arbitrary Function Execution
CVE-2026-6020 - 7.1CVE-2024-4566: ShopLentor <= 2.8.8 WordPress Option Modification
CVE-2024-4566 - 6.5CVE-2025-3775: ShopLentor SSRF
CVE-2025-3775 - 6.4CVE-2026-4059: ShopLentor <= 3.3.5 Stored Cross-Site Scripting
CVE-2026-4059 - 6.4CVE-2025-11823: ShopLentor Stored XSS
CVE-2025-11823
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C