CVE-2025-55046
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 · uneditedMuraCMS through 10.1.10 contains a CSRF vulnerability that allows attackers to permanently destroy all deleted content stored in the trash system through a simple CSRF attack. The vulnerable cTrash.empty function lacks CSRF token validation, enabling malicious websites to forge requests that irreversibly delete all trashed content when an authenticated administrator visits a crated webpage. Successful exploitation of the CSRF vulnerability results in potentially catastrophic data loss within the MuraCMS system. When an authenticated administrator visits a malicious page containing the CSRF exploit, their browser automatically submits a hidden form that permanently empties the entire trash system without any validation, confirmation dialog, or user consent.
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 confidenceMuraCMS through 10.1.10 has a CSRF vulnerability in the cTrash.empty function which lacks CSRF token validation. Attackers can craft malicious webpages that, when visited by an authenticated administrator, automatically submit a hidden form to permanently empty the entire trash system without any confirmation or user consent.
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
- None
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/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.
-
Identify MuraCMS installationLocate the MuraCMS installation directory, typically found in web root folders such as /mura, /Mura, or the application root. Check for the presence of core/modules/v1/external/config Bean.cfc or index.cfm files that confirm MuraCMS presence.Affected if MuraCMS is installed and accessible on the server.
-
Locate the cTrash.empty functionSearch the codebase for the cTrash component or the 'empty' function handling trash operations. Typical paths include core/modules/v1/external/configBean.cfc, core/modules/v1/core/modules/v1/external/configBean.cfc, or under the /admin directory in components related to trash management.Affected if The cTrash.empty function exists in the MuraCMS installation.
-
Examine CSRF token validation in the empty functionOpen the cTrash component file and inspect the empty function for any CSRF token validation logic. Look for parameters such as 'csrfToken', 'csrf_token', 'token', or calls to validation functions like 'validateToken()' or 'checkToken()'. Verify if the function accepts or requires any token parameter before executing the trash emptying operation.Affected if The cTrash.empty function lacks CSRF token validation or does not verify anti-CSRF tokens before processing the request.
-
Verify the empty function accepts requests without tokensReview how the empty function is called. Check if it is exposed through a URL or form submission that does not require a CSRF token. Look for the method signature to see if token validation is mandatory or optional.Affected if The empty function can be triggered via HTTP requests without requiring a valid CSRF token.
If MuraCMS is installed and the cTrash.empty function can be triggered without CSRF token validation, the environment is affected by this vulnerability.
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.
From vendor dataImplement CSRF token validation on the cTrash.empty function to require anti-CSRF tokens for all trash emptying operations.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-55046 — 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-55046 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