Xlinesoft PHPRunner 10.1 dashboard name overlap between protected memory ranges
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability, which was classified as problematic, has been found in Xlinesoft PHPRunner 10.1. This affects an unknown function. Performing a manipulation of the argument dashboard name results in improper handling of overlap between protected memory ranges. This vulnerability is reported as CVE-2019-25592. The attack requires a local approach. Moreover, an exploit is present.
Details
A vulnerability was found in Xlinesoft PHPRunner 10.1. It has been classified as problematic. This affects an unknown functionality. The manipulation of the argument dashboard name with an unknown input leads to a improper handling of overlap between protected memory ranges vulnerability. CWE is classifying the issue as CWE-1260. The product allows address regions to overlap, which can result in the bypassing of intended memory protection. This is going to have an impact on availability. The summary by CVE is:
PHPRunner 10.1 contains a denial of service vulnerability that allows local attackers to crash the application by supplying an excessively long string in the dashboard name field. Attackers can paste a buffer of 10000 characters into the Name field during dashboard creation to trigger an application crash.
The weakness was disclosed by Victor Mondragón as 46824. The advisory is shared at exploit-db.com. This vulnerability is uniquely identified as CVE-2019-25592 since 03/22/2026. The exploitability is told to be easy. An attack has to be approached locally. Technical details and a public exploit are known.
The exploit is shared for download at exploit-db.com. It is declared as proof-of-concept.
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 databases at Exploit-DB (46824) and CNNVD (CNNVD-202603-4154). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 4.7VulDB Meta Temp Score: 4.6
VulDB Base Score: 3.3
VulDB Temp Score: 3.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 6.2
CNA Vector (VulnCheck): 🔒
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: Improper handling of overlap between protected memory rangesCWE: CWE-1260 / CWE-119
CAPEC: 🔒
ATT&CK: 🔒
Physical: Partially
Local: Yes
Remote: No
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Exploit-DB: 🔒
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
03/22/2026 Advisory disclosed03/22/2026 CVE reserved
03/22/2026 VulDB entry created
03/23/2026 VulDB entry last update
Sources
Advisory: 46824Researcher: Victor Mondragón
Status: Not defined
CVE: CVE-2019-25592 (🔒)
GCVE (CVE): GCVE-0-2019-25592
GCVE (VulDB): GCVE-100-352437
CNNVD: CNNVD-202603-4154 - XLineSoft PHPRunner 安全漏洞
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/22/2026 15:50Updated: 03/23/2026 17:29
Changes: 03/22/2026 15:50 (79), 03/23/2026 17:29 (6)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.