CVE-2025-55046 is a CSRF vulnerability affecting MuraCMS versions up to 10.1.10. The vulnerability resides in the cTrash.empty function, which is responsible for emptying the trash system that holds deleted content. This function does not implement CSRF token validation, a critical security control that prevents unauthorized commands from being executed by authenticated users. As a result, an attacker can craft a malicious webpage that, when visited by an authenticated MuraCMS administrator, automatically submits a hidden form request to the vulnerable endpoint. This request causes the trash system to be emptied permanently without any confirmation or user consent, leading to irreversible deletion of all trashed content. The attack requires the victim to be logged in with administrative privileges and simply visit the attacker's webpage. There is no indication that user interaction beyond page visit is necessary, making the attack stealthy and effective. Although no known exploits are currently reported in the wild and no patches have been linked, the vulnerability poses a significant risk to data integrity within affected MuraCMS installations. The lack of CSRF protection in a critical content management function highlights a serious security oversight in the affected versions.

The primary impact of this vulnerability is the permanent loss of all deleted content stored in the trash system of MuraCMS. For organizations relying on MuraCMS for content management, this can result in catastrophic data loss, especially if the trash system is used as a safety net for recovering deleted content. The loss of trashed content could disrupt business operations, cause loss of important historical data, and require costly recovery efforts. Since the attack requires administrative authentication, the scope is limited to environments where administrators access the system via browsers. However, the ease of exploitation—requiring only that an admin visits a malicious webpage—makes it a significant risk. This could also be leveraged as part of a broader attack to degrade system integrity or sabotage content management workflows. The absence of user confirmation or validation increases the likelihood of accidental or malicious data destruction. Although no exploits are currently known in the wild, the vulnerability's existence in a widely used CMS platform means that targeted attacks could emerge, especially against organizations with high-value content or sensitive data.

1. Immediately implement CSRF token validation on the cTrash.empty function and all state-changing endpoints within MuraCMS to ensure requests originate from legitimate sources. 2. Restrict administrative access to trusted networks and use multi-factor authentication to reduce the risk of compromised admin credentials. 3. Educate administrators to avoid visiting untrusted or suspicious websites while logged into the MuraCMS admin interface. 4. Monitor web server logs for unusual POST requests to the trash emptying endpoint that could indicate exploitation attempts. 5. Implement Content Security Policy (CSP) headers to limit the ability of malicious sites to execute unauthorized scripts or submit forms. 6. Regularly back up all content, including trashed items, to enable recovery in case of data loss. 7. Apply principle of least privilege by limiting administrative roles to only those necessary for content management. 8. Stay alert for official patches or updates from MuraCMS and apply them promptly once available. 9. Consider deploying web application firewalls (WAF) with custom rules to detect and block CSRF attack patterns targeting the trash empty function.