CVE-2025-50585
BaseFortify
Publication date: 2025-07-18
Last updated on: 2025-09-09
Assigner: MITRE
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| daycloud | studentmanage | 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. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
CVE-2025-50585 is a SQL injection vulnerability in StudentManage v1.0, specifically in the /admin/adminStudentUrl interface. The vulnerability occurs because the 'query' parameter used for searching is not properly sanitized or validated, allowing attackers to inject malicious SQL code. This can lead to unauthorized database queries and potential data exposure or manipulation. [1]
How can this vulnerability impact me? :
This vulnerability can allow attackers to execute arbitrary SQL commands on the database behind StudentManage v1.0. This could lead to unauthorized access to sensitive data, data modification, or deletion, potentially compromising the integrity and confidentiality of the system's data. [1]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the `query` parameter in the `/admin/adminStudentUrl` endpoint of StudentManage v1.0. You can manually test by injecting SQL payloads such as `' and '1' = '1' --+` and `' and '1' = '2' --+` into the `query` parameter and observing the response for SQL errors or unexpected behavior. Additionally, automated tools like SQLMap can be used to detect and exploit this vulnerability by targeting the `query` parameter to confirm SQL injection. [1]
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include implementing proper input validation and sanitization for the `query` parameter in the `/admin/adminStudentUrl` endpoint. This can be done by using prepared statements, parameterized queries, or input filtering mechanisms to prevent malicious SQL code execution. Until a patch is available, restricting access to the vulnerable endpoint and monitoring for suspicious activity may also help reduce risk. [1]