CVE-2025-10801
BaseFortify
Publication date: 2025-09-22
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 | pet_grooming_management_software | 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?
This vulnerability is a SQL injection flaw in the 'edit_tax.php' file of the SourceCodester Pet Grooming Management Software 1.0. It occurs because the 'id' parameter is not properly validated, allowing attackers to inject malicious SQL queries remotely. This can lead to unauthorized database access. [1]
How can this vulnerability impact me? :
Exploiting this vulnerability can allow attackers to access, modify, or delete sensitive data in the database without authorization. This compromises data integrity and confidentiality, potentially leading to data breaches and loss of trust. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the 'id' parameter in the /admin/edit_tax.php file for SQL injection flaws. You can use tools like sqlmap or manual curl commands to send crafted payloads to the URL and observe if SQL errors or unexpected data are returned. For example, a curl command to test might be: curl -v "http://targetsite/admin/edit_tax.php?id=1' OR '1'='1". Additionally, using sqlmap with the target URL and parameter can automate detection: sqlmap -u "http://targetsite/admin/edit_tax.php?id=1" --batch. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate steps to mitigate this vulnerability include validating and sanitizing the 'id' parameter in the /admin/edit_tax.php file to prevent SQL injection. Implement prepared statements or parameterized queries to handle database inputs securely. Restrict database user permissions to minimize potential damage. Additionally, monitor and block suspicious requests targeting the vulnerable parameter until a patch or update is applied. [1]