CVE-2025-5759
BaseFortify
Publication date: 2025-06-06
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 | local_services_search_engine_management_system | 2.1 |
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-5759 is a critical SQL injection vulnerability in PHPGurukul Local Services Search Engine Management System version 2.1. It occurs in the file /admin/edit-person-detail.php through the editid parameter, which is not properly validated or sanitized. This allows attackers to inject malicious SQL code remotely without authentication, enabling them to manipulate database queries. The flaw arises because user input is directly incorporated into SQL commands without neutralizing special characters, leading to unauthorized database access and potential data compromise. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow remote attackers to read, modify, or delete sensitive data in the database without authentication. It can lead to unauthorized access, data leakage, data tampering, full system compromise, or service disruption. The flaw impacts the confidentiality, integrity, and availability of the affected system, making it critical to remediate immediately to protect system security and data integrity. [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 'editid' parameter in the /admin/edit-person-detail.php file for SQL injection. A common method is to use time-based blind SQL injection payloads, such as appending "AND (SELECT SLEEP(5))" to the 'editid' parameter and observing if the response is delayed, indicating a vulnerability. For example, you can use curl to send a request like: curl "http://target/admin/edit-person-detail.php?editid=2 AND (SELECT SLEEP(5))" and check if the response time increases significantly. This confirms the injection point. Additionally, using automated SQL injection detection tools or scanners targeting this parameter can help identify the vulnerability. [3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implementing prepared statements with parameter binding to ensure user input is not directly included in SQL queries. 2) Applying strict input validation and filtering on the 'editid' parameter to allow only expected input formats. 3) Limiting database user permissions to the minimum necessary, avoiding use of high-privilege accounts such as 'root' or 'admin' for routine database operations. If possible, replacing the affected product or applying patches is recommended. These measures help prevent SQL injection attacks and protect system security and data integrity. [2, 3]