CVE-2025-6863
BaseFortify
Publication date: 2025-06-29
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-6863 is a critical SQL injection vulnerability in PHPGurukul Local Services Search Engine Management System version 2.1. It exists in the /admin/edit-category-detail.php file due to improper validation and sanitization of the 'editid' parameter. This flaw allows attackers to inject malicious SQL code remotely without authentication, enabling unauthorized access to the database. Exploiting this vulnerability can lead to unauthorized data retrieval, modification, or deletion, compromising system security and data integrity. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized access to sensitive data, data leakage, data manipulation, and potential full system compromise. Attackers can retrieve, modify, or delete data in the database, disrupting services and compromising confidentiality, integrity, and availability of the affected system. The vulnerability can be exploited remotely without authentication, increasing the risk of attack. [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-category-detail.php endpoint for SQL injection. One method is to use time-based blind SQL injection payloads such as: editid=1 AND (SELECT SLEEP(5)) to observe delayed responses indicating vulnerability. Tools like sqlmap can be used to automate detection and database enumeration against this parameter. Additionally, Google dorking with queries like 'inurl:admin/edit-category-detail.php' can help identify potentially vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'editid' parameter, and restricting database user permissions to the minimum necessary to reduce impact. Avoid using high-privilege database accounts for routine operations. If possible, consider replacing the affected component with an alternative product to eliminate the vulnerability. [2, 3, 1]