CVE-2025-6403
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 |
|---|---|---|
| fabian | school_fees_payment_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-6403 is a critical SQL injection vulnerability in the School Fees Payment System version 1.0, specifically in the /student.php file. It occurs because the application does not properly validate or sanitize the 'id' parameter in user input, allowing attackers to inject malicious SQL code. This flaw enables unauthorized access to the database, allowing attackers to retrieve, modify, or delete sensitive data remotely without authentication. [1, 2, 3]
How can this vulnerability impact me? :
Exploitation of this vulnerability can lead to unauthorized database access, data modification or deletion, disclosure of sensitive information, full system compromise, and potential denial of service. Since no authentication is required, attackers can remotely exploit this flaw easily, severely impacting 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 'id' parameter in the /student.php file for SQL injection. One effective method is to use sqlmap with a command like: sqlmap -u "http://<target-ip>/student.php?action=delete&id=13" --level 5 --dbs. Additionally, time-based blind SQL injection payloads such as: action=delete&id=13' AND (SELECT SLEEP(5))-- can be used to confirm the injection point by observing delayed responses. Vulnerable targets can also be identified using Google dorking with queries like: inurl:student.php. [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing proper input validation and using parameterized queries or prepared statements to prevent SQL injection. Avoid directly concatenating user input into SQL queries. Since no official vendor patch or mitigation guidance is currently available, replacing the affected component with an alternative product is recommended to avoid exploitation. Additionally, restricting access to the vulnerable endpoint and monitoring for suspicious activity can help reduce risk until a fix is applied. [1, 2, 3]