dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2026-40325

HIGH · 8.7 CVSS v4.0 Published 2026-05-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
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.

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 confidence

Masa CMS versions 7.5.2 and earlier contain a CSRF vulnerability in the cTrash.restore function. The function fails to validate anti-CSRF tokens on content restoration requests, allowing attackers to craft malicious requests that restore deleted items to attacker-controlled locations via the parentid parameter. This enables restoration of malicious content, exposure of sensitive documents in public areas, and disruption of site structure.

MitigationUpgrade to Masa CMS versions 7.2.10, 7.3.15, 7.4.10, or 7.5.3 to receive the CSRF token validation fix. Alternatively, restrict administrative backend access and employ browser isolation for admin sessions.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS 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
Authentication
X
User interaction
P
Scope
X

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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Masa CMS version
    Locate the version file or admin dashboard version information in your Masa CMS installation. Common locations include the admin interface footer or a version manifest file.
    Affected if The installed version is 7.5.2 or earlier, or falls below 7.2.10, 7.3.15, 7.4.10, or 7.5.3 in their respective release branches.
  2. Verify cTrash module is enabled
    Check the Masa CMS admin panel or configuration settings to confirm the content trash/recycle bin module (cTrash) is installed and active.
    Affected if The cTrash module is enabled and accessible to administrative users.
  3. Inspect cTrash.restore function accessibility
    Examine the cTrash component's restore function endpoint. Determine if it is exposed via the web interface and accessible to authenticated administrators.
    Affected if The cTrash.restore function is publicly accessible or accessible to admin users without additional access controls.
  4. Confirm anti-CSRF token validation on restore action
    Review the source code or network requests when performing a content restoration. Check if the restore operation requires and validates an anti-CSRF token.
    Affected if The restore function processes requests without validating an anti-CSRF token, allowing unauthenticated or cross-site requests to succeed.

Your Masa CMS is affected if it runs version 7.5.2 or earlier and the cTrash.restore function is accessible without proper anti-CSRF token validation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Masa CMS versions 7.2.10, 7.3.15, 7.4.10, or 7.5.3 to receive the CSRF token validation fix. Alternatively, restrict administrative backend access and employ browser isolation for admin sessions.

Recommended fix High confidence

If currently on 7.5.x, upgrade to 7.5.3; if on 7.4.x, upgrade to 7.4.10; if on 7.3.x, upgrade to 7.3.15; if on 7.2.x or earlier, upgrade to 7.2.10

  1. 1. Identify the currently running Masa CMS version by checking the admin dashboard or the version file in the installation
  2. 2. Determine the appropriate upgrade path based on your current version (see upgrade_path)
  3. 3. Backup the complete Masa CMS installation including database before upgrading
  4. 4. Download the appropriate fixed version from the official Masa CMS repository (github.com/masacms/masacms)
  5. 5. Follow the official upgrade instructions for your version path, which typically involves replacing core files while preserving configuration and custom assets
  6. 6. Clear all caches after upgrade to ensure new security tokens are properly initialized
  7. 7. Verify the upgrade by logging into the administrative backend and confirming the version number
  8. 8. Test the cTrash.restore functionality to confirm it now properly validates anti-CSRF tokens
Caveat No specific breaking changes mentioned in the advisory; standard upgrade precautions apply (backup first)

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40325 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40325 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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