CVE-2025-6414
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
Can you explain this vulnerability to me?
CVE-2025-6414 is a critical SQL injection vulnerability in the PHPGurukul Art Gallery Management System version 1.1. It occurs in the /admin/changeimage2.php file where the 'editid' parameter is improperly sanitized and directly used in SQL queries. This allows attackers to inject malicious SQL code remotely, manipulating database queries to gain unauthorized access, extract or modify data, and potentially take control of the system. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized database access, data leakage, data manipulation, full system control, and potential service disruption. Attackers can exploit the flaw remotely to compromise the confidentiality, integrity, and availability of the affected system. It may also allow attackers to execute arbitrary SQL commands, leading to severe security breaches. [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the 'editid' parameter in the /admin/changeimage2.php file for SQL injection flaws. You can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://targetsite/agms/admin/changeimage2.php?editid=4" --batch --dbs. Additionally, manual testing can be done using payloads such as: editid=4' AND 5960=5960-- (boolean-based), editid=4' AND (SELECT SLEEP(5))-- (time-based), or UNION-based queries to check for SQL injection. Also, Google dorking with "inurl:admin/changeimage2.php" can help identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Replacing the affected component with an alternative product if possible, as no known patches are currently available. 2) Implementing prepared statements with parameter binding to prevent SQL injection. 3) Applying rigorous input validation and filtering on the 'editid' parameter to ensure it conforms to expected formats. 4) Minimizing database user permissions by avoiding elevated privileges for routine operations. These actions help protect system security and maintain data integrity. [2, 3]