trippleS Digiqole Plugin up to 2.2.7 on WordPress filename control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability described as critical has been identified in trippleS Digiqole Plugin up to 2.2.7 on WordPress. This affects an unknown part. The manipulation results in filename control. This vulnerability is reported as CVE-2025-67527. The attack can be launched remotely. No exploit exists. Upgrading the affected component is recommended.
Details
A vulnerability, which was classified as critical, was found in trippleS Digiqole Plugin up to 2.2.7 on WordPress. Affected is an unknown code block. 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. CVE summarizes:
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in trippleS Digiqole digiqole allows PHP Local File Inclusion.This issue affects Digiqole: from n/a through < 2.2.7.
The weakness was disclosed by João Pedro S Alcântara. The advisory is shared for download at vdp.patchstack.com. This vulnerability is traded as CVE-2025-67527 since 12/09/2025. The exploitability is told to be easy. It is possible to launch the attack remotely. There are neither technical details nor an exploit publicly available.
Upgrading to version 2.2.7 eliminates this vulnerability.
Once again VulDB remains the best source for 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: 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: UpgradeStatus: 🔍
0-Day Time: 🔒
Upgrade: Digiqole Plugin 2.2.7
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-67527 (🔒)
GCVE (CVE): GCVE-0-2025-67527
GCVE (VulDB): GCVE-100-335172
Entry
Created: 12/09/2025 16:01Changes: 12/09/2025 16:01 (56)
Complete: 🔍
Cache ID: 216::103
Once again VulDB remains the best source for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.