# CVE-2025-55044: Cross-site request forgery in n/a

> Attackers can force administrators to restore deleted content to arbitrary locations via CSRF, potentially exposing sensitive data or altering site structure.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 18 Mar 2026
- **Updated:** 19 Mar 2026
- **Also known as:** GHSA-mwfv-gh9m-r5cv

## What is CVE-2025-55044?

CVE-2025-55044 is a high-severity vulnerability in n/a, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

The 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.

Weakness: CWE-352 (Cross-Site Request Forgery)

## Which versions are affected by CVE-2025-55044?

It affects 1 product.


Products: Murasoftware Mura Cms.

## How do I fix CVE-2025-55044?

No fix has been published for CVE-2025-55044 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-55044 being exploited?

There is no known exploitation of CVE-2025-55044 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2025-67829](https://insights.sbomify.com/CVE-2025-67829/): SQL injection in n/a (critical 9.8)
- [CVE-2025-67830](https://insights.sbomify.com/CVE-2025-67830/): SQL injection in n/a (critical 9.8)
- [CVE-2022-47003](https://insights.sbomify.com/CVE-2022-47003/): Auth bypass in n/a (critical 9.8)
- [CVE-2025-55040](https://insights.sbomify.com/CVE-2025-55040/): Cross-site request forgery in n/a (high 8.8)
- [CVE-2025-55046](https://insights.sbomify.com/CVE-2025-55046/): Cross-site request forgery in n/a (high 8.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-55044 and fix it if it is affected.

What it is: CVE-2025-55044 is a high-severity vulnerability in n/a, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-55044 in the wild and no public exploit code.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-55044/ (Markdown: https://insights.sbomify.com/CVE-2025-55044/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-55044
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-55044
- OSV: https://osv.dev/vulnerability/CVE-2025-55044

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-55044/
Summaries are generated and may contain mistakes; the official description above is the record.