CVE-2025-10087
BaseFortify
Publication date: 2025-09-08
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 |
|---|---|---|
| mayuri_k | 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?
CVE-2025-10087 is an authenticated SQL Injection vulnerability in SourceCodester Pet Grooming Management Software version 1.0, specifically in the profit_report.php and sale_report.php files. The vulnerability occurs because the product_id parameter in a POST request is directly concatenated into an SQL query without proper sanitization or use of parameterized queries, despite using PDO. This allows an authenticated attacker to manipulate the SQL query to extract sensitive database information such as database names and financial data. [1, 3]
How can this vulnerability impact me? :
This vulnerability can lead to full disclosure of the database structure and sensitive business data, including financial information. An attacker with admin credentials can execute arbitrary SQL queries, potentially extracting confidential data. Additionally, if combined with other vulnerabilities, it may allow escalation to remote code execution, compromising the integrity and availability of the system. [1, 2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by performing an authenticated SQL injection test on the product_id parameter in the POST request to /admin/profit_report.php. Steps include logging in as an admin, navigating to Reports → Profit Report → Profit Per Product/Service, selecting a product, intercepting the POST request with a proxy tool like Burp Suite, and then using sqlmap to automate the SQL injection test on the saved request. Additionally, vulnerable targets can be identified using Google dorking with the query: inurl:admin/profit_report.php. [1, 2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing parameterized queries with bound parameters to prevent SQL injection, validating that the product_id parameter is numeric and within valid ranges, and applying proper error handling to avoid exposing SQL error messages to users. If possible, consider replacing the affected software with an alternative product. [1, 3, 2]