CVE-2025-6412
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-6412 is a critical SQL injection vulnerability in the PHPGurukul Art Gallery Management System version 1.1. It exists in the /admin/changeimage.php file, specifically involving the 'editid' parameter, which is improperly sanitized and directly embedded into SQL queries. This allows attackers to inject malicious SQL code remotely, enabling unauthorized database operations such as data leakage, manipulation, and potentially full system control. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can impact the confidentiality, integrity, and availability of the affected system. Attackers can perform unauthorized database access, leak sensitive data, manipulate or delete data, gain full system control, and disrupt services. The vulnerability can be exploited remotely with publicly available proof-of-concept exploits, making it a significant security risk. [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/changeimage.php file for SQL injection. Example commands include using sqlmap to test the parameter, e.g., sqlmap -u "http://target/admin/changeimage.php?editid=4" --batch. Manual testing can include sending payloads such as 'editid=4' AND 8892=8892--' for boolean-based blind SQL injection or 'editid=4' AND (SELECT SLEEP(5))--' for time-based blind SQL injection. Additionally, Google dorking with the query inurl:admin/changeimage.php can help identify vulnerable targets. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include replacing the affected software with an alternative product, as no known countermeasures or patches are currently available. Additionally, applying best practices such as using prepared statements with parameter binding to separate SQL code from user input, implementing rigorous input validation and filtering, and minimizing database user permissions can help reduce risk. Prompt remediation is critical to protect system security and data integrity. [2, 3]