Skip to main content
CVE-2024-48655VulnerabilityPublished Updated

CVE-2024-48655: cms · n/a

Affects cmsSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 06:26 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
GitHubtotaljs/cmspkg:github/totaljs/cmsOther threatsAffected
  • =1.0
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-48655, organizations should immediately audit their use of Total.js CMS and identify any instances of version 1.0 in production. Until an official patch is released, consider the following specific actions: 1) Restrict network access to the CMS backend, limiting it to trusted IP addresses or VPNs to reduce exposure. 2) Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious payloads targeting func.js or dynamic code execution attempts. 3) Review and harden server-side configurations to minimize privileges of the CMS process, implementing the principle of least privilege. 4) Monitor logs for unusual activity, especially unexpected code execution or file modifications related to func.js. 5) If feasible, isolate the CMS environment using containerization or sandboxing to limit potential damage. 6) Engage with Total.js maintainers or community to track patch releases and apply updates promptly once available. 7) Consider temporary migration to alternative CMS platforms if risk tolerance is low and patching is delayed.

Description

An issue in Total.js CMS v.1.0 allows a remote attacker to execute arbitrary code via the func.js file.

References

Community reviews

Loading reviews…