Xlinesoft ASPRunner.NET 10.1 Database Table table name reliance on untrusted inputs in a security decision
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability identified as problematic has been detected in Xlinesoft ASPRunner.NET 10.1. Impacted is an unknown function of the component Database Table Handler. The manipulation of the argument table name leads to reliance on untrusted inputs in a security decision. This vulnerability is referenced as CVE-2019-25594. The attack can only be performed from a local environment. Furthermore, an exploit is available.
Details
A vulnerability was found in Xlinesoft ASPRunner.NET 10.1 and classified as problematic. This issue affects some unknown functionality of the component Database Table Handler. The manipulation of the argument table name with an unknown input leads to a reliance on untrusted inputs in a security decision vulnerability. Using CWE to declare the problem leads to CWE-807. The product uses a protection mechanism that relies on the existence or values of an input, but the input can be modified by an untrusted actor in a way that bypasses the protection mechanism. Impacted is availability. The summary by CVE is:
ASPRunner.NET 10.1 contains a denial of service vulnerability that allows local attackers to crash the application by supplying an excessively long string in the table name field. Attackers can input a buffer of 10000 characters in the table name parameter during database table creation to trigger an application crash.
The weakness was published by Victor Mondragón as 46823. The advisory is shared at exploit-db.com. The identification of this vulnerability is CVE-2019-25594 since 03/22/2026. The exploitation is known to be easy. An attack has to be approached locally. Technical details as well as a public exploit are known.
The exploit is available 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 vulnerability database at Exploit-DB (46823). 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: Reliance on untrusted inputs in a security decisionCWE: CWE-807 / CWE-20
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/22/2026 VulDB entry last update
Sources
Advisory: 46823Researcher: Victor Mondragón
Status: Not defined
CVE: CVE-2019-25594 (🔒)
GCVE (CVE): GCVE-0-2019-25594
GCVE (VulDB): GCVE-100-352445
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/22/2026 15:53Changes: 03/22/2026 15:53 (80)
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.