Skip to main content
CVE-2024-45171VulnerabilityPublished Updated

CVE-2024-45171: n/a

Source CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
8.8High
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:L/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Sep 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-25.

What to do

AI-suggested

To mitigate CVE-2024-45171, organizations should immediately restrict access to the backup file upload functionality to only highly trusted administrators and disable it if not essential. Implement strict server-side validation to reject any uploaded files containing executable extensions or suspicious substrings like '.php' regardless of filename. Employ web application firewalls (WAFs) to detect and block attempts to upload or access malicious files in the '/srv/www/backups' directory. Monitor web server logs for unusual access patterns to backup upload URLs and uploaded filenames. Segregate the backup upload directory from the web root or configure the web server to deny execution of scripts in this directory. Enforce the principle of least privilege by reviewing user roles and removing unnecessary upload permissions from low-privileged users. Regularly audit and update the C-MOR system software and apply vendor patches once available. Consider network segmentation to isolate surveillance systems from critical infrastructure to limit lateral movement in case of compromise.

Description

An issue was discovered in za-internet C-MOR Video Surveillance 5.2401. Due to improper user input validation, it is possible to upload dangerous files, for instance PHP code, to the C-MOR system. By analyzing the C-MOR web interface, it was found out that the upload functionality for backup files allows an authenticated user to upload arbitrary files. The only condition is that the filename contains a .cbkf string. Therefore, webshell.cbkf.php is considered a valid file name for the C-MOR web application. Uploaded files are stored within the directory "/srv/www/backups" on the C-MOR system, and can thus be accessed via the URL https://<HOST>/backup/upload_<FILENAME>. Due to broken access control, low-privileged authenticated users can also use this file upload functionality.

References

Community reviews

Loading reviews…