CVE-2025-6096
BaseFortify
Publication date: 2025-06-16
Last updated on: 2026-04-29
Assigner: VulDB
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| codesiddhant | jasmin-ransomware | 1.0.1 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
| CWE-74 | The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-6096 is a critical SQL Injection vulnerability in Jasmin Ransomware version 1.0.1. It exists in the /dashboard.php file through the 'search' parameter, which is improperly sanitized. An attacker can inject malicious SQL code via this parameter, allowing unauthorized database queries or manipulation remotely. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by compromising the confidentiality, integrity, and availability of the affected system. An attacker can remotely exploit the SQL Injection flaw to manipulate or access sensitive database information, potentially leading to data breaches, unauthorized data modification, or disruption of service. [2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /dashboard.php endpoint for SQL injection via the 'search' parameter. One method is to use web vulnerability scanners or manual testing tools like sqlmap targeting the URL with the search parameter. Additionally, Google dorking with queries such as 'inurl:dashboard.php' can help identify potentially vulnerable instances. Example command using sqlmap: sqlmap -u "http://target.com/dashboard.php?search=test" --batch --level=5 --risk=3 [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected Jasmin Ransomware product (up to version 1.0.1) with an alternative solution, as no vendor patches or countermeasures are available. Additionally, restricting access to the /dashboard.php endpoint, implementing web application firewalls (WAF) to block SQL injection attempts, and monitoring for suspicious activity targeting the 'search' parameter can help reduce risk. [2]