CVE-2025-6908
BaseFortify
Publication date: 2025-06-30
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 | old_age_home_management_system | 1.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-6908 is a critical SQL injection vulnerability in PHPGurukul Old Age Home Management System version 1.0. It exists in the /admin/edit-services.php file, specifically involving the 'sertitle' parameter. This parameter is used directly in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. Exploiting this flaw enables attackers to manipulate SQL queries and perform unauthorized database operations remotely. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, full system compromise, and service disruption. Attackers can execute arbitrary SQL commands remotely without authentication, potentially compromising the confidentiality, integrity, and availability of the system. The exploit is publicly available and easy to use, increasing the risk of exploitation. [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 'sertitle' parameter in the /admin/edit-services.php file for SQL injection. A proof-of-concept payload to test is: sertitle=Optional Facilities' RLIKE SLEEP(5)-- which causes a delay in the database response if vulnerable. You can use tools like sqlmap to automate detection, for example: sqlmap -u "http://target/oahms/admin/edit-services.php?id=4" --data="sertitle=Optional Facilities" --technique=T --dbms=MySQL. Additionally, searching for the vulnerable URL pattern using Google dorking such as "inurl:admin/edit-services.php" can help identify 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 'sertitle' parameter, and restricting database user permissions to the minimum necessary, avoiding high-privilege accounts like 'root' or 'admin' for routine operations. If possible, consider replacing the affected product with an alternative solution. [2, 3]