Private Messages for UserPro Plugin up to 4.10.0 on WordPress Private Message filename control
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, was found in Private Messages for UserPro Plugin up to 4.10.0 on WordPress. Affected by this issue is some unknown functionality of the component Private Message Handler. Such manipulation leads to filename control. This vulnerability is referenced as CVE-2025-22311. It is possible to launch the attack remotely. No exploit is available.
Details
A vulnerability, which was classified as problematic, has been found in Private Messages for UserPro Plugin up to 4.10.0 on WordPress. Affected by this issue is some unknown functionality of the component Private Message Handler. The manipulation with an unknown input leads to a filename control vulnerability. Using CWE to declare the problem leads to 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. Impacted is confidentiality, integrity, and availability. CVE summarizes:
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in NotFound Private Messages for UserPro. This issue affects Private Messages for UserPro: from n/a through 4.10.0.
The weakness was published by Bonds. The advisory is shared for download at patchstack.com. This vulnerability is handled as CVE-2025-22311 since 01/03/2025. The exploitation is known to be difficult. The attack may be launched remotely. No form of authentication is required for exploitation. Successful exploitation requires user interaction by the victim. There are neither technical details nor an exploit publicly available.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Once again VulDB remains the best source for vulnerability data.
Product
Type
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
01/03/2025 🔍01/21/2025 🔍
01/21/2025 🔍
02/09/2025 🔍
Sources
Advisory: patchstack.comResearcher: Bonds
Status: Not defined
CVE: CVE-2025-22311 (🔍)
GCVE (CVE): GCVE-0-2025-22311
GCVE (VulDB): GCVE-100-292700
Entry
Created: 01/21/2025 15:53Updated: 02/09/2025 19:30
Changes: 01/21/2025 15:53 (63), 02/09/2025 19:30 (3)
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.