CVE-2024-55506: n/a
Source CVE Database V5
Not known to be exploited · CVSS 8.8 High.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 53% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
AI-suggested
To mitigate CVE-2024-55506, organizations should immediately restrict access to the delete.php endpoint to only highly trusted and authenticated users, ideally through network segmentation or firewall rules. Implement strict authorization checks on the server side to validate user permissions for any object referenced by the 'id' parameter, ensuring users can only delete or access objects they are authorized for. Employ input validation and sanitization to prevent injection or manipulation attacks via the 'id' parameter. Monitor logs for unusual access patterns or repeated attempts to manipulate object references. If possible, disable or remove the delete.php functionality until a vendor patch is available. Conduct a thorough code review of the complaint management system to identify and remediate similar authorization flaws. Additionally, enforce the principle of least privilege for all users and services interacting with the system. Organizations should also prepare incident response plans to quickly address any exploitation attempts. Finally, maintain regular backups of complaint data to enable recovery in case of data loss or corruption.
Description
An IDOR vulnerability in CodeAstro's Complaint Management System v1.0 (version with 0 updates) enables an attacker to execute arbitrary code and obtain sensitive information via the delete.php file and modifying the id parameter.