Skip to main content
VulnerabilityPublished Updated

CVE-2024-31777: openeclass · File Upload

Affects openeclassSource CVE Database V5

0

Public exploit available (Exploit-DB) · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
3.8% chance of exploitation in 30 days – higher than 89% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

t = 0 is the CVE’s publication on cve.org

  1. Disclosed: evidence found.

    CVE published 13 Jun 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

Timeline

  1. CVE ID reserved

    by MITRE Corporation

    , 69 days before disclosure

  2. First Exploit-DB entry (opens in a new tab)

    GUnet OpenEclass E-learning platform 3.15 - 'certbadge.php' Unrestricted File Upload

    , 62 days before disclosure

  3. CVE published

    on cve.org

    , t = 0

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
GitHubfreysolareye/openeclasspkg:github/freysolareye/openeclassOther threatsAffected
  • <=3.15
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2024-31777, organizations should immediately upgrade Open eClass to a patched version once available. In the absence of an official patch, implement the following specific measures: 1) Restrict file upload types strictly to safe formats and reject any executable or script files. 2) Implement server-side validation and sanitization of uploaded files, including verifying MIME types and file extensions. 3) Use secure coding practices to ensure that uploaded files are stored outside the web root or in directories with no execution permissions. 4) Employ web application firewalls (WAFs) to detect and block malicious upload attempts targeting certbadge.php. 5) Monitor server logs and network traffic for unusual activity related to file uploads. 6) Limit access to the certbadge.php endpoint through IP whitelisting or authentication where feasible. 7) Conduct regular security assessments and penetration testing focused on file upload functionalities. These targeted mitigations reduce the attack surface and help prevent exploitation until a formal patch is applied.

Description

File Upload vulnerability in openeclass v.3.15 and before allows an attacker to execute arbitrary code via a crafted file to the certbadge.php endpoint.

References

Community reviews

Loading reviews…