WordPress security changelog
MEDIUM CVE-2026-16797 Deferred

ShopLentor contributors can read unintended WordPress option data

ShopLentor through 3.4.5 exposes GET /wp-json/woolentor/v1/get-wloptions to users who can edit_posts, including Contributors. After nonce validation, get_options_data() accepts attacker-controlled optionSection and optionKey values and passes them to woolentorBlocks_get_option(), which calls get_option(optionSection) and returns the selected nested value. This can disclose arbitrary wp_options records whose values use the expected array-of-arrays structure with title fields, including data belonging to other plugins.

CVE / CNA score 4.3 CVSS 3.1 · security@wordfence.com
NVD score Pending NVD has not published its own CVSS assessment.
Component
ShopLentor – All-in-One WooCommerce Growth & Store Enhancement Plugin
Plugin slug
woolentor-addons
Affected
<= 3.4.5
Safe version
> 3.4.5
Published
Jul 28, 2026
Weakness
CWE-639 — Authorization Bypass Through User-Controlled Key

This CVE was published Jul 28, 2026 and is one of 17 known issues for this plugin.

What to do

Update, patch or deactivate.

Update ShopLentor to a release newer than 3.4.5. The CNA record identifies the affected boundary but does not name a fixed tag; current upstream code allow-lists the WooLentor option and sub-key that this endpoint may return. Review Contributor accounts and requests to the get-wloptions route.

A safe version is available, so updating to that version or later is the preferred remediation. If an immediate update is not practical, consider a targeted application patch or temporarily restricting the affected functionality.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Source record

Technical description

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.

CVE / CNA vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N

References

Primary and upstream sources