CVE-2025-6859
BaseFortify
Publication date: 2025-06-29
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 |
|---|---|---|
| mayurik | best_salon_management_system | 1.0 |
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-6859 is a critical SQL injection vulnerability in SourceCodester Best Salon Management System version 1.0, specifically in the file /panel/pro_sale.php. It occurs due to improper handling of the 'fromdate' and 'todate' parameters, allowing an authenticated attacker to inject malicious SQL code. This can alter the intended SQL queries, potentially leading to unauthorized access or manipulation of the database. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by compromising the confidentiality, integrity, and availability of your system's data. An attacker with valid credentials can exploit the SQL injection to steal sensitive information or damage the underlying database. The attack can be performed remotely, making it easier for attackers to exploit the system without physical access. [1, 2]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by checking for the presence of the vulnerable endpoint `/panel/pro_sale.php` and testing the `fromdate` and `todate` parameters for SQL injection. One detection method is to use Google dorking with the query `inurl:panel/pro_sale.php` to identify potentially vulnerable targets. For direct testing, authenticated users can attempt to inject SQL payloads into the `fromdate` and `todate` parameters to observe if the system is vulnerable. Example command using curl (assuming authentication is handled): `curl -i -X GET 'http://target/panel/pro_sale.php?fromdate=2025-06-01'" OR "1"="1&todate=2025-06-30` to check for SQL injection responses. [2, 1]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations have been documented for this vulnerability. The suggested immediate step is to replace the affected software with an alternative product. Additionally, restricting access to the vulnerable endpoint and ensuring only trusted authenticated users can access the system may reduce risk until a fix or patch is available. [2]