CVE-2024-58276
BaseFortify
Publication date: 2025-12-04
Last updated on: 2025-12-08
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| obi08 | enrollment_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. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability can be detected by sending a crafted POST request to the /get_subject.php endpoint with a malicious 'keyword' parameter designed to trigger SQL injection. For example, using curl, you can run the following command to test for the vulnerability: curl -X POST -d "keyword=emc' union select 1,concat(user_type,'::',username,'::',password),3,4,5,6 from users-- -" http://<target-host>/enrollment_system/get_subject.php If the response contains concatenated user information (user_type, username, password), the system is vulnerable. Additionally, using a Python script similar to the one described in the exploit (Resource 1) can automate detection by sending the payload and parsing the response. [1]
Can you explain this vulnerability to me?
This vulnerability is a SQL injection in the keyword parameter of the /get_subject.php script in Obi08/Enrollment System 1.0. It allows unauthenticated attackers to execute arbitrary SQL queries, including UNION-based injections, to extract sensitive information such as usernames and passwords from the users table.
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized access to sensitive user data, including usernames and passwords. This can result in data breaches, loss of user privacy, potential account takeovers, and compromise of the affected system's integrity and confidentiality.
What immediate steps should I take to mitigate this vulnerability?
Immediate mitigation steps include: 1. Restrict access to the /get_subject.php endpoint to trusted users or internal networks. 2. Implement input validation and parameterized queries (prepared statements) to prevent SQL injection. 3. Apply web application firewall (WAF) rules to detect and block SQL injection payloads targeting the keyword parameter. 4. Monitor logs for suspicious POST requests containing SQL injection patterns. 5. If possible, update or patch the Enrollment System to a version that fixes this vulnerability. 6. As a temporary measure, disable or restrict the vulnerable functionality until a fix is applied.