CVE-2025-6417
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-6417 is a critical SQL injection vulnerability in the PHPGurukul Art Gallery Management System version 1.1. It exists in the /admin/add-artist.php file, specifically in the awarddetails parameter. This parameter is not properly sanitized or validated before being used in SQL queries, allowing attackers to inject malicious SQL code. This can lead to unauthorized manipulation of database queries and execution of arbitrary database commands. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can allow attackers to gain unauthorized access to the database, leading to data leakage, data tampering, and potentially full system compromise or service disruption. The vulnerability affects confidentiality, integrity, and availability of the system. Since it can be exploited remotely without authentication, it poses a severe risk to system security and business continuity. [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 'awarddetails' parameter in the /admin/add-artist.php file for SQL injection. A time-based blind SQL injection test can be performed by sending a crafted POST request with a payload such as: 222' AND (SELECT 5276 FROM (SELECT(SLEEP(5)))ufxl) AND 'WSAu'='WSAu. Monitoring for delayed responses (e.g., 5 seconds delay) indicates a successful injection. Additionally, vulnerable targets can be identified using Google Dorking with the query: inurl:admin/add-artist.php. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing prepared statements with parameter binding to prevent SQL injection, enforcing strict input validation and filtering on the 'awarddetails' parameter, and minimizing database user permissions by avoiding high-privilege accounts for routine operations. Since no known mitigations are documented, replacing the affected component with an alternative product is also suggested to avoid exploitation. [2, 3]