Skip to main content
VulnerabilityPublished Updated

CVE-2024-31022: CandyCMS · Code Injection

Source CVE Database V5

0

Not known to be exploited · 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
0.9% chance of exploitation in 30 days – higher than 60% 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 8 Apr 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

AI-suggested

To mitigate CVE-2024-31022, organizations should immediately restrict or disable access to the install.php component on all CandyCMS installations, especially on production servers. If the install.php script is not required post-installation, it should be removed or renamed to prevent unauthorized access. Implement web application firewall (WAF) rules to detect and block suspicious requests targeting install.php. Monitor web server logs for unusual activity or attempts to exploit this vulnerability. Apply network segmentation and limit exposure of CMS servers to the internet where possible. Stay alert for official patches or updates from CandyCMS developers and apply them promptly once available. Conduct thorough security assessments of CandyCMS deployments to identify and remediate other potential misconfigurations or vulnerabilities. Educate administrators on secure CMS deployment best practices, including disabling or securing installation scripts after setup. Consider deploying intrusion detection systems (IDS) to detect exploitation attempts. Regularly back up CMS data and configurations to enable rapid recovery in case of compromise.

Description

An issue was discovered in CandyCMS version 1.0.0, allows remote attackers to execute arbitrary code via the install.php component.

References

Community reviews

Loading reviews…