CVE-2025-10429
BaseFortify
Publication date: 2025-09-15
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?
CVE-2025-10429 is a SQL injection vulnerability in SourceCodester Pet Grooming Management Software version 1.0, specifically in the /admin/ajax_product.php file. The vulnerability occurs because the application improperly handles the 'drop_services' argument, failing to neutralize special characters in user input. This allows an attacker to inject malicious SQL commands remotely without authentication, potentially manipulating the database in unauthorized ways. [1, 2]
How can this vulnerability impact me? :
This vulnerability can impact you by allowing attackers to execute unauthorized SQL commands on your database remotely. This can compromise the confidentiality, integrity, and availability of your system, potentially leading to data leakage, data modification, or disruption of service. Since the exploit is publicly available and requires no authentication, the risk of exploitation is significant. [1]
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 `/admin/ajax_product.php` and testing the `drop_services` parameter for SQL injection. One method to identify potentially vulnerable targets is using Google Dorking with the query `inurl:admin/ajax_product.php`. For active testing, you can use tools like sqlmap to test the parameter for SQL injection, for example: `sqlmap -u "http://target/admin/ajax_product.php" --data="drop_services=1" --risk=3 --level=5`. Additionally, monitoring network traffic for suspicious SQL injection payloads targeting the `drop_services` parameter can help detect exploitation attempts. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with an alternative product, as no known mitigations or patches are documented. Restricting access to the `/admin/ajax_product.php` file by IP whitelisting or firewall rules can reduce exposure. Additionally, disabling or restricting the vulnerable functionality if possible, and monitoring for exploitation attempts are recommended. Applying input validation and sanitization on the `drop_services` parameter would be ideal but requires code changes. Since the exploit is public and can be launched remotely without authentication, urgent action is advised. [1]