Skip to main content

ShopLentor CVE-2026-92554

| EUVDEUVD-2026-82747 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-09-18 Wordfence GHSA-q87m-52cp-3fm5
6.1
CVSS 3.1 · Vendor: Wordfence
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Craft URL with payload as query-param name
  2. Delivery
    Deliver link to victim (phishing/social)
  3. Exploit
    Victim loads page with Horizontal Filter widget
  4. Execution
    Param name reflected unescaped into value attribute
  5. Persist
    Attribute breakout executes JavaScript
  6. Impact
    Session/action abuse in victim browser context

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Output encoding, context-aware escaping
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires a page that renders the WL: Product Horizontal Filter widget (an Elementor/ShopLentor widget that must be added to a published page) - pages without this widget are not affected. Exploitation is unauthenticated (PR:N) but requires victim user interaction (UI:R): the target must click an attacker-supplied link whose query-string parameter NAME carries the payload, which is reflected into an option element's value="..." attribute without escaping. Impact is limited to reflected (non-persistent) in-browser script execution scoped to the WordPress origin; the higher-value outcome (admin session abuse) requires luring an authenticated administrator. Affected: ShopLentor/WooLentor all versions up to and including 3.5.1.

Impact

This is a genuine but moderate-severity issue. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N, base 6.1) describes an unauthenticated, network-reachable reflected XSS that requires victim user interaction (clicking an attacker-crafted link). Reflected XSS is inherently a per-victim, socially-engineered attack rather than a mass-exploitable server compromise, which caps real-world impact - no confidentiality/integrity of the server itself, only in-browser script execution in the victim's session (C:L/I:L, A:N). No EPSS score, no CISA KEV listing, and no public POC are present in the supplied intelligence, so exploitation status is 'no public exploit identified at time of analysis'; this is not evidence of active exploitation. The scope change (S:C) reflects that injected script executes in the browser's WordPress origin, potentially reaching admin session context if an authenticated admin is lured. Overall this is a standard-priority patch-management item, not an emergency: high install base raises aggregate exposure, but UI:R and the reflected (non-persistent) nature keep individual-target risk contained. Note the fix appears delivered in changeset 3699757 (referenced), though a clean fixed version number is not explicitly stated in the input - verify the exact patched release.

Exploit ScenarioDerived

An attacker crafts a URL to a page rendering the WL: Product Horizontal Filter widget, embedding an XSS payload as a query-string parameter NAME (not value), which the widget reflects unescaped into an option element's value="..." attribute. The attacker sends this link to a victim (e.g., via phishing or a forum post); when the victim clicks and the page loads, the payload breaks out of the attribute context and executes arbitrary JavaScript in their browser under the site's origin. No public POC or active exploitation is identified in the supplied data.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Sep 18, 2026

Reflected cross-site scripting in the ShopLentor (WooLentor Addons) WordPress plugin up to and including version 3.5.1 lets unauthenticated attackers inject arbitrary JavaScript into a page by abusing the name of a query-string parameter, which the WL: Product Horizontal Filter widget reflects unescaped into an option element value attribute. Exploitation requires the victim to click an attacker-supplied link that carries the payload in the parameter name (UI:R) and only works on published pages where that widget has actually been placed, so the result is non-persistent script execution scoped to the WordPress origin; the higher-value outcome, abuse of an authenticated administrator session, requires luring a logged-in admin to the crafted URL. No public exploit code or confirmed in-the-wild exploitation was identified at time of analysis, and the issue is assessed as a genuine but moderate-severity problem (CVSS 6.1, scope-changed reflected XSS) rather than a mass-exploitation candidate.

RemediationAI

Upstream fix available (commit/changeset); a released patched version number is not independently confirmed from the provided data, so the primary action is to update ShopLentor/woolentor-addons to the first plugin release that incorporates Trac changeset 3699757 (https://plugins.trac.wordpress.org/changeset?reponame=&old=3699757%40woolentor-addons&new=3699757%40woolentor-addons) and to continue tracking the Wordfence advisory at https://www.wordfence.com/threat-intel/vulnerabilities/id/0a60b55b-0c76-4b7c-9d16-a3cbd181eb3b?source=cve for the vendor-confirmed fixed version, since no numeric fix version is stated in the available inputs and one should not be assumed. Until the patched build is applied, an effective and low-cost compensating control is to remove or temporarily disable the WL: Product Horizontal Filter widget from all published pages, which eliminates the reflection sink entirely at the cost of losing that storefront filter UI; alternatively, restrict editing and publishing so no new instances of that widget can be deployed during the window. Where a WAF or reverse proxy is available, add a rule that rejects requests whose query-string parameter names contain quote characters, angle brackets, or script-like sequences, understanding that legitimate filtering behavior is unaffected (parameter names are not expected to carry such characters) but that the rule only mitigates this specific reflection path and can be bypassed by encoding tricks if written loosely. Do not rely on generic hardening alone: the sink is client-side and executes in the visitor's browser after the page renders, so server-side output encoding at the plugin's option-generation code is the definitive fix and only the vendor update provides it. Finally, note that pages without the widget are not affected, so triage effort can be prioritized on sites that actually publish it, and administrators should be reminded that clicking untrusted links while logged in is the path to the higher-impact session-abuse scenario.

Affected VersionsENISA

ShopLentor – All-in-One WooCommerce Growth & Store Enhancement Plugin 0 ≤3.5.1

Affected Packages

euvd shoplentor_all_in_one_woocommerce_growth_store_enhancement_plugin no fix

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The flaw is a classic CWE-79 improper neutralization of input during web page generation, specifically the reflected variant, inside the Elementor-based ShopLentor (WooLentor Addons) plugin distributed on WordPress.org as the woolentor-addons package. The vulnerable code lives in includes/addons/wl_product_horizontal_filter.php, around lines 1172 and 1229 (per the linked Trac source references), where the WL: Product Horizontal Filter widget enumerates query-string parameter names from the current request URL and writes them into option element value attributes without output escaping. Because attacker-controlled data lands in an HTML attribute context, a parameter name containing a quote character breaks out of the quoted attribute and permits injection of arbitrary markup and script, which the browser then executes on the WordPress origin. The plugin CPE (devitemsllc:shoplentor_-_all-in-one_woocommerce_growth_&_store_enhancement_plugin) is version-wildcarded, so every released build is treated as in scope; the vendor's Trac changeset 3699757 for woolentor-addons contains the upstream code change addressing this reflection path. The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N confirms network reachability, no privileges required, mandatory user interaction, and a scope change from the vulnerable component to the browser DOM; the assigned score of 6.1 reflects limited confidentiality and integrity impact and no availability impact, consistent with reflected rather than stored script execution.

Know when Shoplentor All In One Woocommerce Growth Store Enhancement Plugin gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY 6.1 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
vuln.today AI 6.1 MEDIUM

Unauthenticated remote reflected XSS (PR:N, AV:N) requiring victim click (UI:R); scope change from browser execution in site origin (S:C) with limited C/I and no availability impact.

3.1 AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:L/VA:N/SC:L/SI:L/SA:N

Primary rating from Vendor (Wordfence).

CVSS VectorVendor: Wordfence

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

DescriptionCVE.org

The ShopLentor - All-in-One WooCommerce Growth & Store Enhancement Plugin plugin for WordPress is vulnerable to Reflected Cross-Site Scripting via Query-String Parameter Name in all versions up to, and including, 3.5.1 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that execute if they can successfully trick a user into performing an action such as clicking on a link. The vulnerability is triggered via the WL: Product Horizontal Filter widget, which reflects attacker-supplied query-string parameter names from the current URL into option element value attributes without escaping, allowing payload breakout from the value="..." attribute context.

Threat Intelligence Overview

EPSS Score
0.3%
Top 81% exploitable
Prevalence
Medium
Popular WooCommerce enhancement plugin (WooLentor/ShopLentor), large but not ubiquitous install base
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

30
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +30
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy