Jakub Glos Sparkle Elementor Kit Plugin up to 2.0.9 on WordPress filename control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Jakub Glos Sparkle Elementor Kit Plugin up to 2.0.9 on WordPress and classified as problematic. Affected by this vulnerability is an unknown functionality. Performing a manipulation results in filename control. This vulnerability is cataloged as CVE-2025-32157. It is possible to initiate the attack remotely. There is no exploit available.
Details
A vulnerability was found in Jakub Glos Sparkle Elementor Kit Plugin up to 2.0.9 on WordPress. It has been classified as problematic. This affects an unknown part. The manipulation with an unknown input leads to a filename control vulnerability. CWE is classifying the issue as 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. This is going to have an impact on 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 Jakub Glos Sparkle Elementor Kit allows PHP Local File Inclusion. This issue affects Sparkle Elementor Kit: from n/a through 2.0.9.
The weakness was shared by João Pedro S Alcântara. The advisory is shared at patchstack.com. This vulnerability is uniquely identified as CVE-2025-32157 since 04/04/2025. The exploitability is told to be difficult. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
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.2VulDB Meta Temp Score: 6.1
VulDB Base Score: 5.0
VulDB Temp Score: 4.8
VulDB Vector: 🔍
VulDB Reliability: 🔍
CNA Base Score: 7.5
CNA Vector (Patchstack): 🔍
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
04/04/2025 🔍04/04/2025 🔍
04/04/2025 🔍
04/04/2025 🔍
Sources
Advisory: patchstack.comResearcher: João Pedro S Alcântara
Status: Not defined
CVE: CVE-2025-32157 (🔍)
GCVE (CVE): GCVE-0-2025-32157
GCVE (VulDB): GCVE-100-303369
Entry
Created: 04/04/2025 18:18Changes: 04/04/2025 18:18 (63)
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.