Opal_WP ekommart Plugin up to 4.3.1 on WordPress php file inclusion
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in Opal_WP ekommart Plugin up to 4.3.1 on WordPress. Affected is an unknown function. Performing a manipulation results in php file inclusion. This vulnerability is cataloged as CVE-2025-67525. It is possible to initiate the attack remotely. There is no exploit available. You should upgrade the affected component.
Details
A vulnerability classified as critical has been found in Opal_WP ekommart Plugin up to 4.3.1 on WordPress. This affects some unknown functionality. The manipulation with an unknown input leads to a php file inclusion 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 Opal_WP ekommart ekommart allows PHP Local File Inclusion.This issue affects ekommart: from n/a through < 4.3.1.
The weakness was shared by João Pedro S Alcântara. The advisory is shared at vdp.patchstack.com. This vulnerability is uniquely identified as CVE-2025-67525 since 12/09/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. Neither technical details nor an exploit are publicly available.
Upgrading to version 4.3.1 eliminates this vulnerability.
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.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
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: Php file inclusionCWE: CWE-98 / CWE-73
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: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: ekommart Plugin 4.3.1
Timeline
12/09/2025 Advisory disclosed12/09/2025 CVE reserved
12/09/2025 VulDB entry created
12/09/2025 VulDB entry last update
Sources
Advisory: vdp.patchstack.comResearcher: João Pedro S Alcântara
Status: Confirmed
CVE: CVE-2025-67525 (🔒)
GCVE (CVE): GCVE-0-2025-67525
GCVE (VulDB): GCVE-100-335169
Entry
Created: 12/09/2025 16:00Changes: 12/09/2025 16:00 (56)
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.