Permanent trash deletion via tokenless forged request
Published Mar 18, 2026 · Updated Mar 18, 2026
CSRF in MuraCMS 10.1.10 and earlier allows remote attackers to permanently delete all trashed content through an administrator's browser. The cTrash.empty function accepts a forged empty-trash request without validating an anti-CSRF token or seeking confirmation. Exploitation requires an authenticated administrator to visit an attacker-controlled page, after which the browser submits the destructive request with the administrator's active session and the trashed content cannot be recovered.
Summary
What happened
CSRF in MuraCMS 10.1.10 and earlier allows remote attackers to permanently delete all trashed content through an administrator's browser. The cTrash.empty function accepts a forged empty-trash request without validating an anti-CSRF token or seeking confirmation. Exploitation requires an authenticated administrator to visit an attacker-controlled page, after which the browser submits the destructive request with the administrator's active session and the trashed content cannot be recovered.
The record
- CVE
- CVE-2025-55046
- Published
- Mar 18, 2026
- Updated
- Mar 18, 2026
- Vendor
- Unknown vendor
- Product
- Unknown product
- Classifications
- CWE-352, CAPEC-62, T1204.001
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Mar 18, 2026CVE publishedPublication date reported by the CVE source.
- Mar 18, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
What conditions does exploitation require?
What is affected?
Affected products and versions are unavailable in this record.
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo