CVE-2019-25594 | Xlinesoft ASPRunner.NET 10.1 Database Table table name reliance on untrusted inputs in a security decision (Exploit 46823 / EDB-46823)

VDB-352445 · CVE-2019-25594 · EXPLOIT 46823 XLINESOFT ASPRUNNER.NET 10.1 DATABASE TABLE TABLE NAME RELIANCE ON UNTRUSTED INPUTS IN A SECURITY DECISION HISTORYDIFFRELATEJSONXMLCTI CVSS Meta Temp Score Current Exploit Price (≈) CTI Interest Score 4.6 $0-$5k 2.71+ Summaryinfo 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. Detailsinfo 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). Productinfo Vendor Xlinesoft Name ASPRunner.NET Version 10.1 CPE 2.3info 🔒 CPE 2.2info 🔒 CVSSv4info VulDB Vector: 🔒 VulDB Reliability: 🔍 CNA CVSS-B Score: 🔒 CNA CVSS-BT Score: 🔒 CNA Vector: 🔒 CVSSv3info VulDB Meta Base Score: 4.7 VulDB 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): 🔒 CVSSv2info 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: 🔍 Exploitinginfo Class: Reliance on untrusted inputs in a security decision CWE: CWE-807 / CWE-20 CAPEC: 🔒 ATT&CK: 🔒 Physical: Partially Local: Yes Remote: No Availability: 🔒 Access: Public Status: Proof-of-Concept Download: 🔒 Price Prediction: 🔍 Current Price Estimation: 🔒 0-Day Unlock Unlock Unlock Unlock Today Unlock Unlock Unlock Unlock Exploit-DB: 🔒 Threat Intelligenceinfo Interest: 🔍 Active Actors: 🔍 Active APT Groups: 🔍 Countermeasuresinfo Recommended: no mitigation known Status: 🔍 0-Day Time: 🔒 Timelineinfo 03/22/2026 Advisory disclosed 03/22/2026 +0 days CVE reserved 03/22/2026 +0 days VulDB entry created 03/22/2026 +0 days VulDB entry last update Sourcesinfo Advisory: 46823 Researcher: 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 Entryinfo Created: 03/22/2026 15:53 Changes: 03/22/2026 15:53 (80) Complete: 🔍 Cache ID: 99:25C:101 Discussion No comments yet. Languages: en. Please log in to comment. ◂ PreviousOverviewNext ▸