ShopLentor <= 3.3.2 - Unauthenticated Email Relay Abuse via 'woolentor_suggest_price_action' AJAX Action
Strategic Overview
- Status
- Patched in 3.3.3
- Affected Version
<= 3.3.2- CVSS
- 8.6High
- Weakness type
- CWE-93 · Improper Neutralization of CRLF Sequences ('CRLF Injection')
- CVE
CVE-2026-1714
At a glance
CVE-2026-1714 is a high-severity Improper Neutralization of CRLF Sequences ('CRLF Injection') vulnerability in the ShopLentor WordPress plugin, affecting versions <= 3.3.2. It carries a CVSS score of 8.6 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 3.3.3; sites on affected versions should update now. Disclosed February 2026, reported by Teerachai Somprasong.
Vulnerability Overview
The ShopLentor – WooCommerce Builder for Elementor & Gutenberg +21 Modules – All in One Solution plugin for WordPress is vulnerable to Email Relay Abuse in all versions up to, and including, 3.3.2 This is due to the lack of validation on the 'send_to', 'product_title', 'wlmessage', and 'wlemail' parameters in the 'woolentor_suggest_price_action' AJAX endpoint. This makes it possible for unauthenticated attackers to send arbitrary emails to any recipient with full control over the subject line, message content, and sender address (via CRLF injection in the 'wlemail' parameter), effectively turning the website into a full email relay for spam or phishing campaigns.
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 privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on integrity.
CWE-93: Improper Neutralization of CRLF Sequences ('CRLF Injection')
The product uses CRLF (carriage return line feeds) as a special element, e.g. to separate lines or records, but it does not neutralize or incorrectly neutralizes CRLF sequences from inputs.
Remediation
Update to version 3.3.3, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: ShopLentor 3.3.3 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 - 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 - 6.4CVE-2025-58990: ShopLentor <= 3.2.0 Stored Cross-Site Scripting
CVE-2025-58990
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C