CVE-2025-6405
Unknown Unknown - Not Provided
BaseFortify

Publication date: 2025-06-21

Last updated on: 2026-04-29

Assigner: VulDB

Description
A vulnerability classified as critical was found in Campcodes Online Teacher Record Management System 1.0. Affected by this vulnerability is an unknown functionality of the file /admin/edit-teacher-detail.php. The manipulation of the argument editid leads to sql injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2025-06-21
Last Modified
2026-04-29
Generated
2026-05-07
AI Q&A
2025-06-21
EPSS Evaluated
2026-05-05
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
campcodes online_teacher_record_management_system 1.0
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
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-6405 is a critical SQL injection vulnerability in Campcodes Online Teacher Record Management System version 1.0. It exists in the file /admin/edit-teacher-detail.php due to improper handling and inadequate validation of the 'editid' parameter. This flaw allows attackers to inject malicious SQL queries remotely without authentication, leading to unauthorized access to the database. Attackers can manipulate the SQL commands executed by the system, potentially exposing, modifying, or deleting sensitive data. [1, 2, 3]


How can this vulnerability impact me? :

Exploitation of this vulnerability can lead to unauthorized data access, modification, and deletion, compromising the confidentiality, integrity, and availability of the system. Attackers can remotely execute arbitrary SQL commands without authentication, potentially causing data leakage, data corruption, denial of service, or even full system compromise. Public proof-of-concept exploits exist, making it easier for attackers to exploit this vulnerability. [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 'editid' parameter in the /admin/edit-teacher-detail.php file for SQL injection. You can use tools like sqlmap to automate detection. Example commands include using sqlmap with the URL parameter, e.g., sqlmap -u "http://target/admin/edit-teacher-detail.php?editid=5" --batch. Additionally, manual testing with payloads such as 'editid=5 AND 6294=6294' (boolean-based blind), 'editid=5;SELECT SLEEP(5) #' (stacked queries), or 'editid=5 UNION ALL SELECT NULL,...' (union-based) can help identify the vulnerability. Google dorking with queries like inurl:admin/edit-teacher-detail.php can help identify vulnerable targets. [2, 3]


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 by separating SQL code from user input. 2) Apply strict input validation and filtering on the 'editid' parameter to ensure it conforms to expected formats. 3) Minimize database user permissions by avoiding high-privilege accounts for application database connections. 4) Conduct regular security audits to detect and fix vulnerabilities promptly. Since no known countermeasures or patches are documented, replacing the affected product with an alternative solution is also suggested. [1, 3, 2]


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart