TangibleWP Listivo Core Plugin up to 2.3.77 on WordPress filename control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability was found in TangibleWP Listivo Core Plugin up to 2.3.77 on WordPress. It has been classified as critical. This affects an unknown function. This manipulation causes filename control. This vulnerability is handled as CVE-2025-67957. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability classified as critical was found in TangibleWP Listivo Core Plugin up to 2.3.77 on WordPress. Affected by this vulnerability is an unknown code block. 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 TangibleWP Listivo Core listivo-core allows PHP Local File Inclusion.This issue affects Listivo Core: from n/a through <= 2.3.77.
The weakness was released by João Pedro S Alcântara. The advisory is shared at patchstack.com. This vulnerability is known as CVE-2025-67957 since 12/15/2025. 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/29/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-4037). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
Vendor
Name
Version
- 2.3.0
- 2.3.1
- 2.3.2
- 2.3.3
- 2.3.4
- 2.3.5
- 2.3.6
- 2.3.7
- 2.3.8
- 2.3.9
- 2.3.10
- 2.3.11
- 2.3.12
- 2.3.13
- 2.3.14
- 2.3.15
- 2.3.16
- 2.3.17
- 2.3.18
- 2.3.19
- 2.3.20
- 2.3.21
- 2.3.22
- 2.3.23
- 2.3.24
- 2.3.25
- 2.3.26
- 2.3.27
- 2.3.28
- 2.3.29
- 2.3.30
- 2.3.31
- 2.3.32
- 2.3.33
- 2.3.34
- 2.3.35
- 2.3.36
- 2.3.37
- 2.3.38
- 2.3.39
- 2.3.40
- 2.3.41
- 2.3.42
- 2.3.43
- 2.3.44
- 2.3.45
- 2.3.46
- 2.3.47
- 2.3.48
- 2.3.49
- 2.3.50
- 2.3.51
- 2.3.52
- 2.3.53
- 2.3.54
- 2.3.55
- 2.3.56
- 2.3.57
- 2.3.58
- 2.3.59
- 2.3.60
- 2.3.61
- 2.3.62
- 2.3.63
- 2.3.64
- 2.3.65
- 2.3.66
- 2.3.67
- 2.3.68
- 2.3.69
- 2.3.70
- 2.3.71
- 2.3.72
- 2.3.73
- 2.3.74
- 2.3.75
- 2.3.76
- 2.3.77
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
12/15/2025 CVE reserved01/22/2026 Advisory disclosed
01/22/2026 VulDB entry created
01/29/2026 VulDB entry last update
Sources
Advisory: patchstack.comResearcher: João Pedro S Alcântara
Status: Not defined
CVE: CVE-2025-67957 (🔒)
GCVE (CVE): GCVE-0-2025-67957
GCVE (VulDB): GCVE-100-342361
EUVD: 🔒
Entry
Created: 01/22/2026 19:07Updated: 01/29/2026 23:38
Changes: 01/22/2026 19:07 (54), 01/29/2026 23:38 (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.