CVE-2025-10079
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 |
|---|---|---|
| phpgurukul | small_crm | 4.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-10079 is a critical SQL injection vulnerability in PHPGurukul Small CRM 4.0, specifically in the /get-quote.php file. The flaw occurs because the 'contact' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, potentially leading to unauthorized database access, data leakage, data manipulation, or disruption of the system. The vulnerability can be exploited using techniques like time-based blind SQL injection. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, modification or deletion of database contents, and potential full system compromise or service disruption. Since it can be exploited remotely without authentication, attackers can leverage it to breach confidentiality, integrity, and availability of the affected system, leading to data loss, corruption, or downtime. [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 testing the /crm/get-quote.php endpoint for SQL injection on the 'contact' parameter. One method is to send a specially crafted POST request with a payload such as: 1234567891' AND (SELECT 4258 FROM (SELECT(SLEEP(5)))gKLb) AND 'BxxU'='BxxU which causes a delay if vulnerable. Tools like sqlmap can be used to automate detection and enumeration of the database via this parameter. Additionally, Google dorking with the query "inurl:get-quote.php" can help identify vulnerable targets. [1, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Applying strict input validation and filtering on the 'contact' parameter to ensure it conforms to expected formats. 3) Minimizing database user privileges by avoiding use of high-privilege accounts such as 'root' or 'admin' for the application database connection. 4) Conducting regular security audits to detect and fix vulnerabilities promptly. If possible, replacing the affected product or component is recommended. [1, 3]