CVE-2025-6346
BaseFortify
Publication date: 2025-06-20
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 |
|---|---|---|
| aown-shah | advance_charity_management_system | 1.0 |
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-6346 is a critical SQL injection vulnerability in the SourceCodester Advance Charity Management System version 1.0, specifically in the file /members/fundDetails.php. The vulnerability occurs due to insufficient input sanitization of the 'm06' GET parameter, allowing an attacker to inject malicious SQL code remotely. This flaw enables time-based blind SQL injection attacks using MySQL's SLEEP() function to cause response delays, which helps attackers confirm the vulnerability and enumerate database information such as schema and table counts. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can lead to unauthorized access to sensitive data, including user credentials and financial records. Attackers can exploit it remotely to extract database schema details and potentially escalate their attack, compromising the confidentiality, integrity, and availability of the affected system. It poses a significant security risk by allowing attackers to enumerate and manipulate database contents. [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 'm06' parameter in the URL /members/fundDetails.php for time-based blind SQL injection. A common method is to send a specially crafted request that uses MySQL's SLEEP() function to cause a delay if the injection is successful. For example, you can use curl or a similar tool to send a request like: curl "http://<target>/members/fundDetails.php?m06=test' AND IF((SELECT COUNT(*) FROM information_schema.tables WHERE table_schema=DATABASE()) > 10, SLEEP(5), 0) AND 'abc'='abc" If the response is delayed by approximately 5 seconds, it indicates the presence of the vulnerability. This technique helps confirm the SQL injection without direct data output by measuring response time delays. [1, 2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include disabling or restricting access to the vulnerable /members/fundDetails.php script, especially the 'm06' parameter, until a patch or fix is applied. Since no known countermeasures or mitigations have been documented, it is recommended to replace the affected software with an alternative product or update to a fixed version if available. Additionally, applying web application firewall (WAF) rules to detect and block SQL injection attempts targeting the 'm06' parameter can help reduce risk. Monitoring and restricting remote access to the affected system is also advised. [3]