CVE-2026-16797
CVE-2026-16797 — ShopLentor <= 3.4.5 - Insecure Direct Object Reference to Authenticated (Contributor+) Sensitive Information Exposure via 'optionSection' Parameter
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.
Published Updated Sources: cvelistV5, Wordfence
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.
Exploitation
Unreported
no source claims exploitation
EPSS
0%
chance of exploitation in 30 days
CVSS base
4.3
MEDIUM
CISA SSVC assessment
Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.
Exploitation
None
none · proof-of-concept · active
Automatable
No
can an attacker script all four kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component
Affected scope
The catalog records vendors and products as separate lists, not pairs, so which product belongs to which vendor is not something this page can say.
Vendors (1)
Products (1)
Every base score collected
Sources score independently and disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Source |
|---|---|---|---|---|---|
| 4.3 | CVSS 3.1 | MEDIUM | — | — | cvelistV5 |
Weakness & attack patterns
- CWE-639
References
6 on the record
- www.wordfence.com/threat-intel/vulnerabilities/id/75d5c684-090e-4fff-9bf7-2b7c41ef95d3?source=cve
reference
- plugins.trac.wordpress.org/browser/woolentor-addons/tags/3.4.5/woolentor-blocks/includes/classes/Api/Api.php#L476
reference
- plugins.trac.wordpress.org/browser/woolentor-addons/tags/3.4.5/woolentor-blocks/includes/helper-functions.php#L7
reference
- plugins.trac.wordpress.org/browser/woolentor-addons/tags/3.4.5/woolentor-blocks/includes/classes/Api/Api.php#L143
reference
- plugins.trac.wordpress.org/browser/woolentor-addons/tags/3.4.5/woolentor-blocks/includes/classes/Api/Api.php#L168
reference
- plugins.trac.wordpress.org/changeset?reponame=&old=3623166%40woolentor-addons&new=3623166%40woolentor-addons
reference
Elsewhere on this site
- devitemsllcevery CVE for this vendor
- CWE-639other pages naming this weakness
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.