CVE-2025-55044
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Trash Restore CSRF vulnerability in MuraCMS through 10.1.10 allows attackers to restore deleted content from the trash to unauthorized locations through CSRF. The vulnerable cTrash.restore function lacks CSRF token validation, enabling malicious websites to forge requests that restore content to arbitrary parent locations when an authenticated administrator visits a crafted webpage. Successful exploitation of the Trash Restore CSRF vulnerability results in unauthorized restoration of deleted content to potentially inappropriate or malicious locations within the MuraCMS website structure. When an authenticated administrator visits a malicious webpage containing the CSRF exploit, their browser automatically submits a hidden form that restores specified content from the trash to a location determined by the attacker through the parentid parameter. This can lead to restoration of previously deleted malicious content, placement of sensitive documents in public areas, manipulation of website navigation structure, or restoration of outdated content that was intentionally removed for security or compliance reasons.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe cTrash.restore function in MuraCMS through version 10.1.10 lacks CSRF token validation, allowing authenticated administrators to be tricked into restoring deleted content to arbitrary parent locations via a malicious website containing a hidden form that submits the parentid parameter.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE dataall versionsCVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Confirm MuraCMS installationCheck your web application for MuraCMS by looking for the /core/modules/v1/external/configurator.cfm file, or by logging into the admin dashboard at /admin and checking the footer version infoAffected if MuraCMS is present and accessible via /admin
-
Locate cTrash componentFind the cTrash.cfc component in your Mura installation, typically in /core/modules/v1/core/modules/v1/external/entities/ or search for 'component cTrash' in the codebaseAffected if The cTrash component exists in the Mura installation
-
Examine restore function for CSRF protectionOpen the cTrash.cfc file and inspect the restore function - search for 'function restore' or 'remote function restore' and check if there is any code validating a CSRF token, antiCSRF, or token parameterAffected if The restore function exists and contains NO code that validates a CSRF token, antiCSRF token, or session token before executing the restore operation
-
Verify admin authentication requirementCheck if the restore function has role='admin' or similar access control by examining the function declaration and any security annotationsAffected if The function requires admin authentication but does NOT validate CSRF tokens on the restore action
You are affected if MuraCMS is installed and the cTrash.restore function does not include server-side CSRF token validation before restoring content, allowing attackers to trick authenticated administrators into restoring deleted content to attacker-controlled parent locations via hidden forms.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedImplement CSRF token validation on the cTrash.restore function and require valid tokens for all restore operations.
MuraCMS version greater than 10.1.10 (check www.murasoftware.com for the specific fixed release)
- 1. Check Mura Software's official security advisories and release notes at www.murasoftware.com for information on CVE-2025-55044 and available patches
- 2. If a patch is available, apply it according to Mura's patch installation instructions
- 3. If no patch is immediately available, verify that your instance is not exposing the trash management interface to unauthenticated users
- 4. As a temporary mitigation, warn administrators against browsing untrusted sites while authenticated to MuraCMS
- 5. Monitor Mura's official channels for security updates addressing the CSRF vulnerability in cTrash.restore
- 6. After applying any fix, verify that the restore function now requires valid CSRF token validation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55044 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-55044 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data