CVE-2025-6489
BaseFortify
Publication date: 2025-06-22
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 |
|---|---|---|
| adonesevangelista | agri-trading_online_shopping_system | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| 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. |
| 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-6489 is a critical SQL injection vulnerability in the Agri-Trading Online Shopping System version 1.0, specifically in the /transactionsave.php file. It occurs because the 'del' parameter is not properly validated or sanitized before being used in SQL queries. This allows attackers to inject malicious SQL code remotely without authentication, enabling unauthorized access to the database, data leakage, modification, or deletion of data, and potentially full system compromise. [1, 2, 3]
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, modification or deletion of database records, disruption of services, and potentially full system compromise. Attackers can exploit the flaw remotely without authentication, leading to loss of data integrity, confidentiality, and availability, which can severely affect business continuity and system security. [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 /transactionsave.php endpoint for SQL injection via the 'del' parameter. One suggested method is using the sqlmap tool with a command like: python sqlmap.py --random-agent -u "http://<target-ip>:<port>/transactionsave.php?action=adds" --data="del=2023-01-01" --dbs. Additionally, attackers may be located by searching for URLs containing 'transactionsave.php' using Google dorking techniques such as "inurl:transactionsave.php". [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Using prepared statements with parameter binding to prevent SQL injection. 2) Implementing strict input validation and filtering on the 'del' parameter to ensure it conforms to expected formats. 3) Minimizing database user permissions by avoiding high-privilege accounts for routine operations. 4) Conducting regular security audits to detect and fix vulnerabilities promptly. If possible, replacing the affected component with an alternative product is recommended. [1, 2, 3]