Skip to main content
VulnerabilityPublished Updated

CVE-2024-48180: ClassCMS · Unrestricted File Upload

Affects ClassCMSSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 48% 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

  1. Disclosed: evidence found.

    CVE published 16 Oct 2024

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

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

    Not in CISA KEV and no source reports exploitation

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

    No attack traffic recorded by OffSeq Mirage sensors

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
GitHubj-0k3r/ClassCMSpkg:github/j-0k3r/ClassCMSOther threatsAffected
  • <=4.8
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-48180, organizations should immediately: 1) Apply any available patches or updates from ClassCMS developers once released. 2) If patches are not yet available, restrict write permissions to the /class/template directory to prevent unauthorized file uploads. 3) Implement strict input validation and sanitization on file uploads, ensuring only safe file types are accepted and verifying file contents. 4) Employ web application firewalls (WAFs) with rules to detect and block attempts to access or include files in the vulnerable path. 5) Monitor logs for suspicious upload or inclusion activity related to /class/template directory. 6) Consider isolating or sandboxing the CMS environment to limit the impact of potential exploitation. 7) Conduct regular security audits and vulnerability scans to detect similar file inclusion or upload issues. 8) Educate development teams on secure coding practices to prevent CWE-434 type vulnerabilities in future releases.

Description

ClassCMS <=4.8 is vulnerable to file inclusion in the nowView method in/class/cms/cms.php, which can include a file uploaded to the/class/template directory to execute PHP code.

References

Community reviews

Loading reviews…