CVE-2025-8179
BaseFortify
Publication date: 2025-07-26
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-8179 is a critical SQL injection vulnerability in PHPGurukul Local Services Search Engine Management System version 2.1. It exists in the /admin/changeimage.php file, specifically in the 'editid' parameter, which is improperly sanitized. This allows attackers to inject malicious SQL queries remotely without authentication, leading to unauthorized database access, data leakage, data tampering, and potentially full system compromise. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can allow attackers to remotely execute arbitrary SQL commands on the affected system without authentication. This can lead to unauthorized access to sensitive data, modification or deletion of data, data leakage, and potentially full system compromise. The integrity, confidentiality, and availability of the system and its data can be severely impacted. [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 /admin/changeimage.php endpoint with the editid parameter for SQL injection. Techniques include Boolean-based blind SQL injection (e.g., editid=25 AND 3977=3977), time-based blind SQL injection (e.g., editid=25 AND (SELECT SLEEP(5))), stacked queries (e.g., editid=25;SELECT SLEEP(5) #), and UNION-based SQL injection payloads. Tools like sqlmap can be used to confirm the vulnerability by enumerating databases. Additionally, searching for the vulnerable URL using Google dorking with "inurl:admin/changeimage.php" can help identify targets. Example sqlmap command: sqlmap -u "http://target/admin/changeimage.php?editid=25" --batch --dbs [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected product with an alternative if possible. If continuing to use the product, implement prepared statements with parameter binding to separate SQL code from user input, apply strict input validation and filtering on the editid parameter to ensure it conforms to expected formats, and minimize database user privileges by avoiding high-privilege accounts for routine operations. These measures help prevent unauthorized data access, maintain data integrity, and secure the system. [2, 3]