Top-Password SQL Server Password Changer 1.90 Registration User Name/Registration Code out-of-bounds write
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.6 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in Top-Password SQL Server Password Changer 1.90 and classified as critical. The affected element is an unknown function of the component Registration Handler. This manipulation of the argument User Name/Registration Code causes out-of-bounds write. This vulnerability is handled as CVE-2019-25475. It is possible to launch the attack on the local host. Additionally, an exploit exists.
Details
A vulnerability was found in Top-Password SQL Server Password Changer 1.90. It has been declared as problematic. Affected by this vulnerability is an unknown part of the component Registration Handler. The manipulation of the argument User Name/Registration Code with an unknown input leads to a out-of-bounds write vulnerability. The CWE definition for the vulnerability is CWE-787. The product writes data past the end, or before the beginning, of the intended buffer. As an impact it is known to affect availability. The summary by CVE is:
SQL Server Password Changer 1.90 contains a buffer overflow vulnerability that allows local attackers to crash the application by supplying an oversized payload. Attackers can inject 6000 bytes of data into the User Name and Registration Code field to trigger a denial of service condition.
The weakness was released by Velayutham Selvaraj and Praveen Thiyagarayam as 47318. The advisory is shared at exploit-db.com. This vulnerability is known as CVE-2019-25475 since 02/23/2026. The exploitation appears to be easy. An attack has to be approached locally. Technical details and also a public exploit are known.
It is possible to download the exploit 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.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Type
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: Out-of-bounds writeCWE: CWE-787 / 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 |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
02/23/2026 CVE reserved03/11/2026 Advisory disclosed
03/11/2026 VulDB entry created
03/14/2026 VulDB entry last update
Sources
Advisory: 47318Researcher: Velayutham Selvaraj, Praveen Thiyagarayam
Status: Not defined
CVE: CVE-2019-25475 (🔒)
GCVE (CVE): GCVE-0-2019-25475
GCVE (VulDB): GCVE-100-350521
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/11/2026 19:57Updated: 03/14/2026 18:07
Changes: 03/11/2026 19:57 (81), 03/14/2026 18:07 (1)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.