CVE-2025-6411
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-6411 is a critical SQL injection vulnerability in PHPGurukul Art Gallery Management System version 1.1, specifically in the /admin/changepropic.php file. The vulnerability arises because the 'imageid' parameter is directly used in SQL queries without proper sanitization or validation, allowing attackers to inject malicious SQL code. This enables attackers to manipulate SQL queries arbitrarily and perform unauthorized database operations remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data leakage, data manipulation, full system control, and potential service disruption. Attackers can remotely exploit the flaw without authentication, making it easy to launch attacks that compromise the confidentiality, integrity, and availability of the affected system. [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 'imageid' parameter in the /admin/changepropic.php file for SQL injection. You can use tools like sqlmap targeting the 'imageid' parameter to enumerate databases and confirm the vulnerability. Example payloads include boolean-based blind injection (e.g., imageid=2' AND 2821=2821--), time-based blind injection using MySQL SLEEP (e.g., imageid=2' AND (SELECT 4555 FROM (SELECT(SLEEP(5)))uloO)--), and UNION-based injection to extract data. A sample command using sqlmap would be: sqlmap -u "http://target/agms/admin/changepropic.php?imageid=2" --risk=3 --level=5 --batch [3, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to separate SQL code from user input, preventing injection. 2) Enforce strict input validation and filtering on the 'imageid' parameter to ensure it conforms to expected formats. 3) Restrict database user permissions to the minimum necessary, avoiding use of high-privilege accounts for routine operations. Additionally, consider replacing the affected software with an alternative product to avoid exploitation, as no known countermeasures are documented. [3, 2]