CVE-2025-6409
BaseFortify
Publication date: 2025-06-21
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 | art_gallery_management_system | 1.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
How can this vulnerability impact me? :
Exploiting this vulnerability can allow attackers to execute arbitrary SQL commands remotely without authentication. This can lead to unauthorized access to sensitive data, data leakage, data manipulation, and potentially full system compromise. The confidentiality, integrity, and availability of the affected system can be severely impacted. [2, 3]
Can you explain this vulnerability to me?
CVE-2025-6409 is a critical SQL injection vulnerability in PHPGurukul Art Gallery Management System version 1.1. It occurs in the /admin/forgot-password.php file where the 'email' parameter is improperly handled and directly incorporated into SQL queries without proper sanitization or validation. This allows attackers to inject malicious SQL code remotely, enabling unauthorized database operations such as data leakage, manipulation, or full system compromise without authentication. [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/forgot-password.php endpoint, specifically the 'email' parameter, for SQL injection. Tools like sqlmap can be used to automate detection by sending crafted inputs to the 'email' parameter to check for SQL injection vulnerabilities, including time-based blind SQL injection techniques (e.g., using MySQL SLEEP function). Additionally, vulnerable targets can be identified using Google dorking with queries such as 'inurl:admin/forgot-password.php'. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to separate SQL code from user input, enforcing rigorous input validation and filtering on the 'email' parameter, and minimizing database user permissions by avoiding high-privilege accounts for routine operations. Since no known mitigations or countermeasures have been published, it is also recommended to replace the affected software with an alternative product if possible. [2, 3]