Skip to content
Web

CVE-2026-1714

8.6
High
EPSS 0.65%Patch availableFeb 18, 2026

Unauthenticated email-relay via ShopLentor WP plugin (CRLF) through AJAX endpoint.

common questions

Is CVE-2026-1714 being exploited?

Not confirmed. CVE-2026-1714 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.65% probability of exploitation in the next 30 days.

How severe is CVE-2026-1714?

CVE-2026-1714 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-1714?

Yes. A fix has been recorded for CVE-2026-1714. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-1714 affect?

CVE-2026-1714 affects WordPress, ShopLentor – WooCommerce Builder for Elementor & Gutenberg (WP plugin), Woolentor_suggest_price_action AJAX endpoint. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-1714?

Patch to latest version; validate inputs; restrict outbound mail.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
WordPressShopLentor – WooCommerce Builder for Elementor & Gutenberg (WP plugin)Woolentor_suggest_price_action AJAX endpoint
impact

Unauthenticated CRLF injection enables sending arbitrary emails with forged sender/subject, turning the site into a spam/phishing relay.

action required

Patch when possible

affected versions
devitemsllc ShopLentor – All-in-One WooCommerce Growth & Store Enhancement Plugin
  • affected<= 3.3.2

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free