CVE-2025-5675
BaseFortify
Publication date: 2025-06-05
Last updated on: 2025-06-10
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
How can this vulnerability impact me? :
This vulnerability can have severe impacts including unauthorized access to sensitive data, data tampering, deletion or modification of records, and potential disruption of services. Attackers can exploit the flaw remotely without authentication, which increases the risk. It may lead to loss of data integrity, confidentiality breaches, and availability issues, potentially resulting in full system compromise. [1, 2, 3]
Can you explain this vulnerability to me?
CVE-2025-5675 is a critical SQL injection vulnerability in Campcodes Online Teacher Record Management System version 1.0, specifically in the file /trms/admin/bwdates-reports-details.php. The vulnerability occurs because the application improperly handles the 'fromdate' and 'todate' parameters, allowing attackers to inject malicious SQL code. This can lead to unauthorized access to the database, data leakage, modification, or deletion of data, and potentially full system control. The attack can be performed remotely without authentication. [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 vulnerable endpoint /trms/admin/bwdates-reports-details.php for SQL injection using specially crafted payloads. For example, a time-based blind SQL injection payload like "fromdate=2025-06-02' AND (SELECT 4427 FROM (SELECT(SLEEP(5)))IRAO) AND 'NhDa'='NhDa" can be used to observe delays in response time indicating injection. Additionally, the sqlmap tool can be used with the command: sqlmap -u "http://<target>/trms/admin/bwdates-reports-details.php" --data="fromdate=2025-06-02&todate=2025-06-05&submit=" to automate detection of the SQL injection vulnerability. Vulnerable targets can also be identified using Google dorking with the query: inurl:trms/admin/bwdates-reports-details.php [2, 3]
What immediate steps should I take to mitigate this vulnerability?
Immediate steps to mitigate this vulnerability include: 1) Using prepared statements with parameter binding to separate SQL code from user input, preventing injection; 2) Implementing strict input validation and filtering to ensure inputs conform to expected formats; 3) Minimizing database user permissions by avoiding use of high-privilege accounts for routine operations; 4) Conducting regular security audits of code and systems to detect and fix vulnerabilities promptly. Since no known countermeasures or patches are documented, replacing the affected product or applying these coding best practices is recommended to secure the system. [2, 3]