Skip to main content
VulnerabilityPublished Updated

CVE-2025-55046: MuraCMS · CVE-2025-55046 is a high-severity CSRF

Source CVE Database V5

0

Not known to be exploited · CVSS 8.1 High.

Data as of 26 Oct 2026, 15:59 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Mar 2026

  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-2025-55046, organizations should immediately implement the following measures: 1) Restrict administrator access to trusted networks and devices to reduce exposure to malicious webpages. 2) Educate administrators about the risks of visiting untrusted websites while logged into MuraCMS and enforce strict browsing policies. 3) Employ web application firewalls (WAFs) to detect and block suspicious CSRF attack patterns targeting the cTrash.empty function. 4) Monitor administrator activity logs for unusual trash emptying events and establish alerting mechanisms. 5) Regularly back up all content, including trashed items, to enable recovery in case of data loss. 6) If possible, apply custom patches or temporary CSRF token validation on the cTrash.empty endpoint until an official patch is released. 7) Use browser security features such as SameSite cookies to reduce CSRF risks. 8) Limit the number of administrators with trash-emptying privileges to minimize the attack surface. These steps go beyond generic advice by focusing on operational controls, monitoring, and temporary technical mitigations in the absence of an official patch.

Description

CVE-2025-55046 is a high-severity CSRF vulnerability in MuraCMS versions through 10.1.10 that allows attackers to permanently delete all trashed content. The vulnerability exists because the cTrash.empty function does not validate CSRF tokens, enabling malicious websites to forge requests that empty the trash system when an authenticated administrator visits a crafted webpage. Exploitation requires the administrator to interact with a malicious page, which then automatically submits a hidden form to irreversibly delete trashed content without confirmation. This results in significant data loss impacting the integrity and availability of content within MuraCMS. No known exploits are currently in the wild, and no patches have been linked yet. Organizations using MuraCMS should be aware of this risk and take immediate mitigation steps to prevent data destruction.

References

Community reviews

Loading reviews…