CVE-2025-66947
SQL Injection in krishanmuraiji SMS Admin Module Enables Data Compromise
Publication date: 2025-12-26
Last updated on: 2025-12-26
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| krishanmuraiji | sms | 1.0 |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-UNKNOWN |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a SQL injection in the krishanmuraiji SMS version 1.0, specifically in the /studentms/admin/edit-class-detail.php file via the editid GET parameter. An attacker can exploit this by using SQL SLEEP() commands to cause controlled delays, which allows them to infer the contents of the database. This means the attacker can extract information from the database by measuring response times.
How can this vulnerability impact me? :
The vulnerability can lead to a full database compromise, especially since it exists within an administrative module. This means an attacker could potentially access, modify, or delete sensitive data stored in the database, leading to data breaches and loss of data integrity.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by testing the /studentms/admin/edit-class-detail.php endpoint with the editid GET parameter for SQL injection, specifically by injecting SQL commands that cause controlled delays such as using the SQL SLEEP() function. For example, you can use curl or a browser to send requests like: curl 'http://target/studentms/admin/edit-class-detail.php?editid=1 AND SLEEP(5)' and observe if the response is delayed, indicating vulnerability. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include validating and sanitizing all user inputs, especially the editid GET parameter, to prevent SQL injection. Use prepared statements or parameterized queries in the code to handle database queries safely. Additionally, restrict access to the administrative module and monitor for suspicious activity until a patch or update is applied. [1]