ShopLentor <= 3.4.5 - Insecure Direct Object Reference to Authenticated (Contributor+) Sensitive Information Exposure via 'optionSection' Parameter
Strategic Overview
- Status
- Patched in 3.4.6
- Affected Version
<= 3.4.5- CVSS
- 4.3Medium
- Weakness type
- CWE-639 · Authorization Bypass Through User-Controlled Key
- CVE
CVE-2026-16797
At a glance
CVE-2026-16797 is a medium-severity Authorization Bypass Through User-Controlled Key vulnerability in the ShopLentor WordPress plugin, affecting versions <= 3.4.5. 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 3.4.6; sites on affected versions should update now. Disclosed July 2026, reported by Wordfence PRISM.
Vulnerability Overview
The ShopLentor – All-in-One WooCommerce Growth & Store Enhancement Plugin plugin for WordPress is vulnerable to Insecure Direct Object Reference in all versions up to, and including, 3.4.5 via the 'optionSection' parameter due to missing validation on a user controlled key. This makes it possible for authenticated attackers, with contributor-level access and above, to read arbitrary wp_options rows — including internal plugin news feed data, WooCommerce block pattern transients, and third-party configuration records — whose values are stored as arrays-of-arrays containing 'title' keys, enabling cross-plugin data leakage.
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-639: Authorization Bypass Through User-Controlled Key
ShopLentor <= 3.4.5 carries this weakness at optionSection, and reaching it takes an account at Contributor level or above. Authorization bypass through a user-controlled key, often called insecure direct object reference, means the application looks up a record by an identifier from the request without checking that the caller owns it.
Changing a number in the request is enough to read or modify other users' records, which on commerce and membership sites means customer data. For ShopLentor the fix is 3.4.6: builds <= 3.4.5 are affected, anything from 3.4.6 onward is not.
Remediation
Update to version 3.4.6, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: ShopLentor 3.4.6 closes this, and updating the plugin is the step that ends it.
- Login Security
- 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