dbcve.org
ShoplentorWordPress extension · Hasthemes

CVE-2025-3775

MEDIUM · 6.5 CVSS v3.1 Published 2025-04-25
Fix available
A fix is available. Upgrade to 3.1.3 or later.
See remediation →
74/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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 summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Server-Side Request Forgery (SSRF) vulnerability in the woolentor_template_proxy function of the ShopLentor WordPress plugin. Unauthenticated attackers can make the web server perform requests to arbitrary URLs, potentially accessing internal services, reading metadata, or pivoting to internal systems.

MitigationUpdate ShopLentor plugin to version 3.1.3 or later. If immediate update is not possible, disable the plugin or implement WAF rules to block requests to the woolentor_template_proxy endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ShoplentorWordPress extension
Affected:< 3.1.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Locate the ShopLentor plugin installation
    Access your WordPress site via FTP or file manager and navigate to /wp-content/plugins/woolentor-addons/ or check the plugin directory listing via SSH. The main plugin file (usually woolentor-addons.php or index.php) contains the version in the plugin header.
    Affected if The plugin folder 'woolentor-addons' exists in the plugins directory and contains a PHP file with a version declaration.
  2. Determine the installed plugin version
    Open the main plugin PHP file and look for the 'Version:' field in the plugin header comment, or check the changelog/readme.txt file for the version number.
    Affected if The version number found is less than 3.1.3 (for example, 3.1.2, 3.1.1, 3.0.x, etc.).
  3. Check if the woolentor_template_proxy endpoint exists
    Examine the plugin source files for the woolentor_template_proxy function. Search for 'woolentor_template_proxy' in the PHP files within the plugin directory using grep or a file search.
    Affected if The function woolentor_template_proxy is present in the plugin code, indicating the vulnerable code path exists.
  4. Verify the endpoint is accessible
    Send a test HTTP request to yourdomain.com/wp-admin/admin-ajax.php?action=woolentor_template_proxy (or the specific endpoint path if different) using curl or a browser. Check if the server accepts and processes the request without authentication.
    Affected if The endpoint responds and does not require authentication, allowing unauthenticated access to the proxy functionality.

Your environment is affected if ShopLentor plugin version is below 3.1.3 AND the woolentor_template_proxy endpoint is present and accessible without authentication.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.1.3 or later
Fixed in 3.1.3
Interim mitigation

Update ShopLentor plugin to version 3.1.3 or later. If immediate update is not possible, disable the plugin or implement WAF rules to block requests to the woolentor_template_proxy endpoint.

Recommended fix High confidence

3.1.3

  1. Update the ShopLentor (formerly WooLentor) plugin to version 3.1.3 or later
  2. Verify the update was successful by checking the plugin version in WordPress admin > Plugins
  3. Confirm the woolentor_template_proxy function is no longer vulnerable by ensuring the plugin is updated

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Shoplentor Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-3775 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-3775 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data