CVE-2025-6404
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 |
|---|---|---|
| campcodes | online_teacher_record_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-6404 is a critical SQL injection vulnerability in Campcodes Online Teacher Record Management System version 1.0, specifically in the /admin/search.php file. The vulnerability occurs because the 'searchdata' parameter is not properly validated or sanitized, allowing attackers to inject malicious SQL queries. This 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? :
This vulnerability can lead to unauthorized database access, data leakage, data tampering, and potentially full system control. Attackers can exploit it remotely without authentication, causing service disruption and compromising the confidentiality, integrity, and availability of the system's data. [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 /trms/admin/search.php endpoint for SQL injection via the 'searchdata' POST parameter. You can use tools like sqlmap to automate detection. Example sqlmap command: sqlmap -u "http://target/trms/admin/search.php" --data="searchdata=123" --risk=3 --level=5 --batch. Additionally, manual testing can be done by sending payloads such as 'searchdata=123' AND (SELECT SLEEP(5))-- to observe response delays indicating time-based blind SQL injection. [2]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1) Implement prepared statements with parameter binding to prevent SQL injection. 2) Apply strict input validation and sanitization on the 'searchdata' parameter. 3) Limit database user permissions to avoid using high-privilege accounts for routine operations. 4) Conduct regular security audits and code reviews. If possible, consider replacing the affected product with a secure alternative. [2, 3]