# CVE-2025-12493: ShopLentor <= 3.2.5 - Unauthenticated Local PHP File Inclusion via 'load_template'

> Unauthenticated attackers can include and execute arbitrary PHP files via the load_template function, leading to code execution or data disclosure.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Nov 2025
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-rgx4-r686-q8hp

## What is CVE-2025-12493?

CVE-2025-12493 is a critical path traversal vulnerability in devitemsllc ShopLentor – All-in-One WooCommerce Growth & Store Enhancement Plugin, published on 4 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The ShopLentor – WooCommerce Builder for Elementor & Gutenberg +21 Modules – All in One Solution (formerly WooLentor) plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 3.2.5 via the 'load_template' function. This makes it possible for unauthenticated attackers to include and execute arbitrary .php files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where .php file types can be uploaded and included.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2025-12493?

It affects 1 product.


Products: Hasthemes Shoplentor.

## How do I fix CVE-2025-12493?

No fix has been published for CVE-2025-12493 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-12493 being exploited?

There is no known exploitation of CVE-2025-12493 in the wild and no public exploit code.

## Other vulnerabilities in devitemsllc ShopLentor – All-in-One WooCommerce Growth & Store Enhancement Plugin

- [CVE-2023-0232](https://insights.sbomify.com/CVE-2023-0232/): ShopLentor < 2.5.4 - PHP Object Injection (critical 9.8)
- [CVE-2024-4566](https://insights.sbomify.com/CVE-2024-4566/): ShopLentor <= 2.8.8 - Missing Authorization to WordPress Option Modification (high 7.1)
- [CVE-2025-58990](https://insights.sbomify.com/CVE-2025-58990/): WordPress ShopLentor Plugin <= 3.2.0 - Cross Site Scripting (XSS) Vulnerability (medium 6.5)
- [CVE-2025-3775](https://insights.sbomify.com/CVE-2025-3775/): Server-side request forgery in ShopLentor – All-in-One WooCommerce Growth & Store Enhancement Plugin (medium 6.5)
- [CVE-2024-34767](https://insights.sbomify.com/CVE-2024-34767/): WordPress ShopLentor plugin <= 2.8.7 - Cross Site Scripting (XSS) vulnerability (medium 6.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-12493 and fix it if it is affected.

What it is: CVE-2025-12493 is a critical path traversal vulnerability in devitemsllc ShopLentor – All-in-One WooCommerce Growth & Store Enhancement Plugin, published on 4 Nov 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-12493 in the wild and no public exploit code.

Affected product: devitemsllc ShopLentor – All-in-One WooCommerce Growth & Store Enhancement Plugin. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-12493/ (Markdown: https://insights.sbomify.com/CVE-2025-12493/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-12493
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-12493
- OSV: https://osv.dev/vulnerability/CVE-2025-12493

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-12493/
Summaries are generated and may contain mistakes; the official description above is the record.