CVE-2025-10114
BaseFortify
Publication date: 2025-09-09
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-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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-10114 is a critical SQL injection vulnerability in PHPGurukul Small CRM version 4.0, specifically in the /profile.php file. The vulnerability occurs because the application does not properly validate or sanitize the 'name' parameter, allowing attackers to inject malicious SQL code. This enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, data leakage, data tampering, and potentially full system compromise or service disruption. Attackers can modify or delete data, retrieve sensitive information, and disrupt the availability and integrity of the affected system. The attack can be performed remotely without any authentication, making it highly dangerous. [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 'name' parameter in the /profile.php file for SQL injection. One method is to use a time-based blind SQL injection payload, such as sending a specially crafted POST request with the payload `111' AND (SELECT 1197 FROM (SELECT(SLEEP(5)))VdUy) AND 'NuBw'='NuBw` in the 'name' parameter to observe if the database response is delayed, indicating vulnerability. Additionally, automated tools like sqlmap can be used to confirm the SQL injection by extracting database information. Attackers may also identify vulnerable targets using Google dorking with queries like `inurl:profile.php`. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to separate SQL code from user inputs, preventing injection. 2) Applying strict input validation and filtering to ensure inputs conform to expected formats. 3) Minimizing database user permissions by avoiding use of high-privilege accounts for routine operations. 4) Conducting regular security audits to detect and fix vulnerabilities promptly. If possible, consider replacing the affected product with an alternative solution as no known mitigations are documented. Prompt remediation is necessary to secure the system and maintain data integrity. [1, 3, 2]