CVE-2020-37113
Gunet Open Eclass Platform 1.7.3
Raw vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XSummary
CVE-2020-37113 is a high-severity Unrestricted Upload of File with Dangerous Type (CWE-434) vulnerability in Gunet Open Eclass Platform. Its CVSS base score is 8.7 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked in the top 48% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) and SI-2 (Flaw Remediation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
GUnet OpenEclass 1.7.3 contains a file upload vulnerability (CVE-2020-37113, CWE-434) in its exercise submission feature that allows authenticated users to bypass intended file extension restrictions. Attackers can rename a PHP file to extensions like .php3 or .PhP, enabling the upload of a web shell. This flaw leads to remote code execution on the server, with a CVSS v3.1 base score of 8.8 (AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H).
Any authenticated user with access to the platform can exploit this vulnerability remotely with low complexity and no user interaction required. Successful exploitation allows the attacker to upload and execute arbitrary code via the web shell, potentially compromising the entire server through full control over confidentiality, integrity, and availability.
Mitigation details are outlined in the official CHANGES.txt file at https://download.openeclass.org/files/docs/1.7/CHANGES.txt. Additional resources include a proof-of-concept exploit at https://www.exploit-db.com/exploits/48163, the OpenEclass website at https://www.openeclass.org/, and a Vulncheck advisory at https://www.vulncheck.com/advisories/gunet-openeclass-e-learning-platform-file-upload-extension-bypass.
A public exploit is available on Exploit-DB, indicating potential for real-world abuse in unpatched e-learning environments.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2020-30982
Vulnerability Data
GUnet OpenEclass 1.7.3 allows authenticated users to bypass file extension restrictions when uploading files. By renaming a PHP file to .php3 or .PhP, an attacker can upload a web shell and execute arbitrary code on the server. This vulnerability enables…
more
remote code execution by bypassing the intended file type checks in the exercise submission feature.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise TechniquesAI
Why these techniques?
The vulnerability is a file upload bypass in a public-facing web application (e-learning platform) that directly enables exploitation of public-facing applications (T1190) and facilitates deployment of a web shell for remote code execution (T1100).
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
Mitigating Controls (NIST 800-53 r5) AI
Directly mitigates the file extension bypass by requiring validation of uploaded files' types and contents to prevent web shell execution.
Addresses the specific flaw in OpenEclass exercise submission by ensuring timely patching as detailed in the official CHANGES.txt.
Detects and blocks malicious code like renamed PHP web shells during or after upload attempts.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Restricting execution of unauthorized software directly blocks dangerous uploaded files from running.
Hardened configuration baselines can enforce allowed file types and processing rules.
Secure development practices include input validation and file-type restrictions that prevent this weakness.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Configuration and acceptance testing verify that file-upload handling enforces allowed types and does not permit dangerous content to be stored or executed.
Secure-coding guidelines and security testing explicitly address restrictions on allowed file types and upload handling, reducing the risk that dangerous file uploads are accepted without validation.
Mandated testing for malicious content and known vulnerabilities reduces the likelihood that an outsourced component will contain or accept dangerous file types that could later be uploaded or executed.
Application allow-listing and pre-use scanning of received files directly blocks the introduction of executable content that has not been vetted, eliminating the primary vector for unrestricted dangerous file uploads.