# CVE-2026-40325: Masa CMS CSRF in content restoration allows unauthorized restoration of deleted content

> Attackers can trick admins into restoring deleted content to attacker-controlled locations, exposing sensitive data or disrupting site integrity.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:L/SC:N/SI:N/SA:N`)
- **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:** 6 May 2026
- **Updated:** 7 May 2026
- **Also known as:** GHSA-3mpf-gq73-crxf

## What is CVE-2026-40325?

CVE-2026-40325 is a high-severity vulnerability in MasaCMS, published on 6 May 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

Masa CMS is a content management system forked from Mura CMS. In versions 7.5.2 and earlier, the `cTrash.restore` function does not properly validate anti-CSRF tokens for content restoration requests. An attacker can trick a logged-in administrator to submit a forged request that restores deleted items from the trash and places them at an attacker-controlled location in the site structure through the parentid parameter. This can restore previously deleted malicious or outdated content, expose sensitive documents by moving them into publicly accessible locations, and disrupt site structure or content integrity.

This issue has been fixed in versions 7.2.10, 7.3.15, 7.4.10, and 7.5.3. As a workaround, restrict access to the administrative backend, use browser isolation for administrative sessions, and regularly empty the trash to reduce the amount of content available for unauthorized restoration.

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

## Which versions are affected by CVE-2026-40325?


## How do I fix CVE-2026-40325?

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

## Is CVE-2026-40325 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-40325 and fix it if it is affected.

What it is: CVE-2026-40325 is a high-severity vulnerability in MasaCMS, published on 6 May 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-2026-40325 in the wild and no public exploit code.

Affected product: MasaCMS. 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-2026-40325/ (Markdown: https://insights.sbomify.com/CVE-2026-40325/index.md)
```

## Sources

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

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