CVE-2025-6880
BaseFortify
Publication date: 2025-06-30
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-6880 is a critical SQL injection vulnerability in SourceCodester Best Salon Management System version 1.0, specifically in the file /panel/edit-tax.php via the editid parameter. This flaw allows an attacker to manipulate SQL queries due to improper input sanitization, enabling them to execute arbitrary SQL commands remotely. The vulnerability requires authentication according to one source, but another states it can be exploited remotely without authentication. Exploits are publicly available, making it easier for attackers to leverage this vulnerability. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to steal sensitive information, modify or delete data, and cause damage to the database. It affects the confidentiality, integrity, and availability of the system. Since the exploit is publicly available and can be executed remotely, it poses a significant risk to systems running the affected software, potentially leading to data breaches or service disruptions. [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 file `/panel/edit-tax.php` and testing the `editid` parameter for SQL injection flaws. One method is to use Google dorking with the query `inurl:panel/edit-tax.php` to identify potentially vulnerable targets. Additionally, manual or automated SQL injection testing tools can be used to test the `editid` parameter for injection. Since the vulnerability requires authentication, testing should be performed with valid credentials. Specific commands are not provided in the resources. [2, 1]
What immediate steps should I take to mitigate this vulnerability?
No known countermeasures or mitigations are currently available for this vulnerability. It is recommended to replace the affected product with an alternative. Immediate steps include restricting access to the vulnerable endpoint, monitoring for suspicious activity, and applying any available updates or patches if released by the vendor. Since the exploit is publicly available and easy to use, consider isolating or disabling the vulnerable functionality until a fix is implemented. [2]