Elated-Themes Laurent Core Plugin up to 2.4.1 on WordPress filename control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability marked as critical has been reported in Elated-Themes Laurent Core Plugin up to 2.4.1 on WordPress. This issue affects some unknown processing. This manipulation causes filename control. This vulnerability is tracked as CVE-2026-24608. The attack is possible to be carried out remotely. No exploit exists.
Details
A vulnerability classified as critical was found in Elated-Themes Laurent Core Plugin up to 2.4.1 on WordPress. Affected by this vulnerability is an unknown code. The manipulation with an unknown input leads to a filename control vulnerability. The CWE definition for the vulnerability is CWE-98. The PHP application receives input from an upstream component, but it does not restrict or incorrectly restricts the input before its usage in "require," "include," or similar functions. As an impact it is known to affect confidentiality, integrity, and availability. The summary by CVE is:
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Elated-Themes Laurent Core laurent-core allows PHP Local File Inclusion.This issue affects Laurent Core: from n/a through <= 2.4.1.
The weakness was disclosed by Phat Rio. The advisory is shared at patchstack.com. This vulnerability is known as CVE-2026-24608 since 01/23/2026. The exploitation appears to be easy. The attack can be launched remotely. Neither technical details nor an exploit are publicly available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/24/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-4333). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Filename controlCWE: CWE-98
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
01/23/2026 Advisory disclosed01/23/2026 CVE reserved
01/23/2026 VulDB entry created
01/24/2026 VulDB entry last update
Sources
Advisory: patchstack.comResearcher: Phat Rio
Status: Not defined
CVE: CVE-2026-24608 (🔒)
GCVE (CVE): GCVE-0-2026-24608
GCVE (VulDB): GCVE-100-342577
EUVD: 🔒
Entry
Created: 01/23/2026 16:26Updated: 01/24/2026 07:02
Changes: 01/23/2026 16:26 (54), 01/24/2026 07:02 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.