CVE-2020-37112
Multiple SQL Injection Vulnerabilities in GUnet OpenEclass
Publication date: 2026-02-03
Last updated on: 2026-02-12
Assigner: VulnCheck
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gunet | open_eclass_platform | 1.7.3 |
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 does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
[{'type': 'paragraph', 'content': 'The vulnerability in GUnet OpenEclass 1.7.3 allows authenticated attackers to perform SQL injection attacks that can extract sensitive database information. This exposure of sensitive data can lead to non-compliance with data protection regulations such as GDPR and HIPAA, which require the protection of personal and sensitive information from unauthorized access and breaches.'}, {'type': 'paragraph', 'content': "Specifically, the ability to extract sensitive information through SQL injection compromises confidentiality, a core requirement in these standards. Additionally, the presence of plaintext password storage and unauthorized access to other users' data further increases the risk of violating privacy and security controls mandated by such regulations."}] [2, 3]
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': "GUnet OpenEclass version 1.7.3 contains multiple SQL injection vulnerabilities that allow authenticated attackers to manipulate database queries by exploiting unvalidated input parameters, such as the 'month' parameter in the agenda module and other endpoints."}, {'type': 'paragraph', 'content': 'Attackers can use error-based or time-based SQL injection techniques to extract sensitive information from the database. These vulnerabilities are classified under CWE-89 (Improper Neutralization of Special Elements used in an SQL Command).'}] [2, 3]
How can this vulnerability impact me? :
[{'type': 'paragraph', 'content': 'This vulnerability can lead to significant impacts including unauthorized extraction of sensitive database information, such as user data and credentials.'}, {'type': 'list_item', 'content': 'Attackers with authenticated access can exploit SQL injection to retrieve full database contents rapidly.'}, {'type': 'list_item', 'content': 'Unauthenticated attackers can perform slower time-based blind SQL injection to potentially retrieve administrator credentials.'}, {'type': 'list_item', 'content': "Additional vulnerabilities allow file upload bypasses enabling remote code execution, unauthorized access to other students' assessments, and exposure of plaintext passwords."}, {'type': 'paragraph', 'content': 'Overall, these issues can compromise confidentiality and integrity of the system, potentially leading to data breaches and unauthorized system control.'}] [2, 3]
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "This vulnerability can be detected by testing the 'month' parameter in the agenda module (modules/agenda/myagenda.php) for SQL injection using error-based or time-based techniques."}, {'type': 'paragraph', 'content': 'One practical approach is to use automated SQL injection tools like sqlmap to test the parameter for injection vulnerabilities.'}, {'type': 'paragraph', 'content': "An example payload to test error-based SQL injection on the 'month' parameter is:"}, {'type': 'list_item', 'content': "month=5' AND (SELECT 9183 FROM(SELECT COUNT(*),CONCAT(0x7170717671,(SELECT (ELT(9183=9183,1))),0x716b706b71,FLOOR(RAND(0)*2))x FROM INFORMATION_SCHEMA.PLUGINS GROUP BY x)a)--"}, {'type': 'paragraph', 'content': 'Using sqlmap, a command to test the vulnerability might look like:'}, {'type': 'list_item', 'content': 'sqlmap -u "http://[target]/modules/agenda/myagenda.php?month=5" --cookie="[auth_cookie]" --risk=3 --level=5 --dbs'}, {'type': 'paragraph', 'content': 'Note that authentication is required to exploit most SQL injection points, so valid credentials or session cookies are necessary.'}] [2]
What immediate steps should I take to mitigate this vulnerability?
[{'type': 'paragraph', 'content': 'Immediate mitigation steps include:'}, {'type': 'list_item', 'content': 'Restrict access to the vulnerable Open eClass 1.7.3 platform to trusted users only, as exploitation requires authenticated access.'}, {'type': 'list_item', 'content': "Apply input validation and sanitization on all parameters, especially the 'month' parameter in the agenda module and other endpoints."}, {'type': 'list_item', 'content': 'If possible, upgrade to a newer, patched version of Open eClass that addresses these SQL injection vulnerabilities.'}, {'type': 'list_item', 'content': 'Monitor and audit database queries and web server logs for suspicious activity indicating SQL injection attempts.'}, {'type': 'list_item', 'content': 'Limit privileges of authenticated users to the minimum necessary to reduce the impact of potential exploitation.'}, {'type': 'paragraph', 'content': 'Additionally, consider disabling or restricting access to modules that allow file uploads or other risky operations until patches are applied.'}] [2, 3]