CVE-2025-6467
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 |
|---|---|---|
| fabian | online_bidding_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-6467 is a critical SQL injection vulnerability in the Online Bidding System version 1.0, specifically in the /login.php file. The vulnerability occurs because the 'user' parameter in the login form is not properly validated or sanitized, allowing attackers to inject malicious SQL code. This enables unauthorized manipulation of SQL queries, potentially giving attackers access to the backend database to retrieve, modify, or delete sensitive data. [1, 2, 3]
How can this vulnerability impact me? :
Exploiting this vulnerability can lead to unauthorized database access, allowing attackers to leak sensitive information, tamper with or delete data, gain full system control, and cause service interruptions. This threatens data integrity, system security, and business continuity. The attack requires no authentication and can be performed remotely, making it easy to exploit. [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 /login.php endpoint for SQL injection on the 'user' parameter. Common detection methods include using automated tools like sqlmap to send crafted payloads to the login.php page. Example sqlmap command: sqlmap -u "http://target/login.php" --data="user=codeprojects&password=anything" --risk=3 --level=5 --batch. Additionally, manual testing can be done using payloads such as 'user=codeprojects%' OR NOT 9171=9171 # to check for boolean-based blind SQL injection, or time-based payloads like 'user=codeprojects%' AND (SELECT SLEEP(5)) -- to observe response delays indicating injection. Google Dorking with queries like inurl:login.php can help identify vulnerable targets on the network. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameterized queries to prevent SQL injection by separating SQL code from user input. 2) Apply strict input validation and sanitization on the 'user' parameter to ensure only expected input formats are accepted. 3) Minimize database user privileges by avoiding use of high-privilege accounts such as 'root' or 'admin' for application database access. 4) Conduct regular security audits and code reviews to detect and fix vulnerabilities promptly. If possible, replace the affected component with a secure alternative. These steps help prevent exploitation and protect data integrity and system availability. [1, 3]