CVE-2025-6607
BaseFortify
Publication date: 2025-06-25
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-6607 is a critical SQL injection vulnerability in SourceCodester Best Salon Management System 1.0, specifically in the /panel/stock.php file. It occurs due to improper handling of the 'ID' parameter, which allows an attacker to inject malicious SQL commands remotely. This flaw can compromise the confidentiality, integrity, and availability of the system. [1, 2]
How can this vulnerability impact me? :
This vulnerability can allow an attacker to remotely execute malicious SQL commands, potentially leading to unauthorized disclosure of sensitive data, modification or deletion of database information, and disruption of system availability. Exploitation requires valid user credentials, but once exploited, it can severely impact the security and operation of the affected system. [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/stock.php and testing the 'ID' parameter for SQL injection. One method is to use Google dorking with the query "inurl:panel/stock.php" to identify potentially vulnerable targets. For direct testing, you can use tools like sqlmap or manual curl commands to inject SQL payloads into the 'ID' parameter and observe the response for SQL errors or unexpected behavior. Example command: curl -G "http://target/panel/stock.php" --data-urlencode "ID=1' OR '1'='1". Note that exploitation requires authentication, so testing should be done with valid credentials. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations have been reported for this vulnerability. The suggested immediate step is to replace the affected product with an alternative solution. Additionally, restricting access to the vulnerable endpoint, applying strict input validation, and monitoring for suspicious activity may help reduce risk until a patch or fix is available. [1]