CVE-2026-24673
File Upload Validation Bypass in Open eClass Before
Publication date: 2026-02-03
Last updated on: 2026-02-10
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| gunet | open_eclass_platform | to 4.2 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-434 | The product allows the upload or transfer of dangerous file types that are automatically processed within its environment. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
[{'type': 'paragraph', 'content': 'CVE-2026-24673 is a moderate severity vulnerability affecting Open eClass versions up to 4.1. It involves a file upload validation bypass where attackers can upload files with prohibited extensions by embedding them inside ZIP archives.'}, {'type': 'paragraph', 'content': 'The application restricts file uploads based on file extensions, but this restriction can be bypassed by compressing a disallowed file (e.g., shell.php) into a ZIP archive and uploading it without triggering automatic extraction.'}, {'type': 'paragraph', 'content': "Attackers then use the application's user interface to manually extract the archive on the server, causing the prohibited file to be written to the target directory, circumventing the intended file type restrictions."}, {'type': 'paragraph', 'content': 'This vulnerability is classified under CWE-434 (Unrestricted Upload of File with Dangerous Type) and does not imply execution of the uploaded server-side files.'}] [1]
How can this vulnerability impact me? :
This vulnerability allows an attacker with some user privileges to upload unauthorized files with prohibited extensions to the server by bypassing file upload restrictions.
While it does not allow direct execution of these files, it can lead to unauthorized modification of files on the server, potentially compromising the integrity of the system.
The attack requires network access and low complexity, but no user interaction, making it relatively easy to exploit by an attacker with limited privileges.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
[{'type': 'paragraph', 'content': "This vulnerability involves uploading ZIP archives containing prohibited file types and manually extracting them via the Open eClass application's interface. Detection can focus on identifying suspicious ZIP file uploads and the presence of disallowed files extracted on the server."}, {'type': 'list_item', 'content': 'Monitor file upload logs for ZIP archive uploads, especially from users with low privileges.'}, {'type': 'list_item', 'content': 'Check the server directories used by Open eClass for the presence of prohibited file extensions (e.g., .php) that should not be allowed.'}, {'type': 'list_item', 'content': "Use commands to find suspicious files, for example, on the server: `find /path/to/openeclass/uploads -type f -name '*.php'` to locate unexpected PHP files."}, {'type': 'list_item', 'content': 'Inspect web server access logs for unusual extraction actions or file upload activities.'}] [1]
What immediate steps should I take to mitigate this vulnerability?
The primary mitigation step is to upgrade the Open eClass platform to version 4.2 or later, where this vulnerability has been patched.
- Restrict file upload permissions to trusted users only.
- Temporarily disable the ability to upload ZIP archives or disable manual extraction functionality if upgrading immediately is not possible.
- Implement additional server-side validation to prevent extraction or storage of prohibited file types.
- Regularly audit uploaded files and server directories for unauthorized or suspicious files.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The vulnerability allows attackers to bypass file upload restrictions by embedding prohibited files inside ZIP archives and extracting them on the server, leading to unauthorized modification of files.
While the vulnerability does not impact confidentiality or availability, the unauthorized file upload and modification could potentially lead to non-compliance with standards and regulations that require strict control over data integrity and security, such as GDPR and HIPAA.
However, the provided information does not explicitly state the direct impact on compliance with these regulations.