CVE-2025-6410
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-6410 is a critical SQL injection vulnerability in PHPGurukul Art Gallery Management System version 1.1. It exists in the /admin/edit-art-medium-detail.php file, specifically involving the 'editid' parameter. This parameter is used directly in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. This can lead to unauthorized database operations such as data leakage, data manipulation, or even full system compromise. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can allow attackers to remotely execute arbitrary SQL commands on the affected system. This can result in unauthorized access to sensitive data, modification or deletion of data, and potentially full control over the system. It can also disrupt service availability and compromise the confidentiality, integrity, and availability of the system. [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-art-medium-detail.php file for SQL injection. You can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://target/admin/edit-art-medium-detail.php?editid=1" --risk=3 --level=5 --batch. Additionally, manual testing with payloads such as "editid=6' AND (SELECT 3619 FROM (SELECT(SLEEP(5)))zDCR)--" can help detect time-based blind SQL injection. Google dorking can also identify vulnerable targets using queries like "inurl:admin/edit-art-medium-detail.php". [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection by separating SQL code from user input. 2) Enforce strict input validation and filtering on the 'editid' parameter to ensure it conforms to expected formats. 3) Limit database user permissions to the minimum necessary to reduce impact if exploited. Since no known countermeasures are documented, replacing the affected component with an alternative product is recommended if possible. [2, 3]