CVE-2025-3775

ShopLentor – WooCommerce Builder for Elementor & Gutenberg +20 Modules – All in One Solution (formerly WooLentor) <= 3.1.2 - Unauthenticated Server-Side Request Forgery via URL Parameter

2025-04-24 16:21
mikemyers

Strategic Overview

Status
Patched in 3.1.3
Affected Version
<= 3.1.2
CVSS
6.5Medium
Weakness type
CWE-918 · Server-Side Request Forgery (SSRF)
CVE
CVE-2025-3775
View all ShopLentor – All-in-One WooCommerce Growth & Store Enhancement Plugin vulnerabilities

At a glance

CVE-2025-3775 is a medium-severity Server-Side Request Forgery (SSRF) vulnerability in the ShopLentor WordPress plugin, affecting versions <= 3.1.2. It carries a CVSS score of 6.5 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.1.3; sites on affected versions should update now. Disclosed April 2025, reported by mikemyers.

Vulnerability Overview

The ShopLentor – WooCommerce Builder for Elementor & Gutenberg +20 Modules – All in One Solution (formerly WooLentor) plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 3.1.2 via the woolentor_template_proxy function. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application, and can be used to query and modify information from internal services.

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.

CWE-918: Server-Side Request Forgery (SSRF)

Reaching this weakness in ShopLentor <= 3.1.2 takes no account at all. Server-side request forgery means the application fetches a URL supplied by the caller, turning the server into a proxy for requests the attacker could not make directly.

The request originates from inside the hosting network, which is how these flaws reach cloud metadata endpoints, internal admin panels and services that trust local traffic. For ShopLentor the fix is 3.1.3: builds <= 3.1.2 are affected, anything from 3.1.3 onward is not.

Remediation

Update to version 3.1.3, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: ShopLentor 3.1.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Login Security
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C