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

CVE-2026-40309

HIGH · 7.2 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 →
79/100
Remediation priority · High
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.empty function does not validate anti-CSRF tokens for trash management requests. An attacker can induce a logged-in administrator to submit a forged request that empties the trash and permanently deletes all deleted content. This can cause irreversible data loss and disrupt recovery of content intended for restoration. 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 maintain current database backups to recover from unauthorized deletion.

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 lack anti-CSRF token validation in the cTrash.empty function, allowing attackers to trick authenticated administrators into submitting forged requests that permanently delete all trash contents.

MitigationApply vendor patches (7.2.10, 7.3.15, 7.4.10, or 7.5.3) to implement proper CSRF token validation; as interim measures, restrict admin backend access, use browser isolation, and maintain backups.

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:N/VI:H/VA:H/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. Confirm Masa CMS installation
    Identify if Masa CMS is present in your environment by checking for its characteristic directory structure, configuration files, or web application fingerprint.
    Affected if Masa CMS is not installed - you are not affected.
  2. Determine installed Masa CMS version
    Locate and read the version identifier from the Masa CMS installation (commonly found in build files, admin panel about section, or version configuration).
    Affected if Version is 7.5.2 or earlier, or any 7.2.x, 7.3.x, 7.4.x release - proceed to next check.
  3. Verify admin backend access
    Confirm you have authenticated access to the Masa CMS administrator backend.
    Affected if You have admin backend access and the version is in the affected range - you are potentially affected.
  4. Confirm cTrash module availability
    Check if the cTrash.empty function is accessible in your installation (typically found under content management or trash management features).
    Affected if The cTrash.empty function exists and is accessible without CSRF protection - you are affected.

You are affected if Masa CMS is installed with a version 7.5.2 or earlier (including 7.2.x, 7.3.x, 7.4.x) and you have authenticated administrator access to the cTrash.empty function.

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

Apply vendor patches (7.2.10, 7.3.15, 7.4.10, or 7.5.3) to implement proper CSRF token validation; as interim measures, restrict admin backend access, use browser isolation, and maintain backups.

Recommended fix High confidence

7.5.3 (for 7.5.x) or 7.4.10/7.3.15/7.2.10 depending on current branch

  1. 1. Identify the current version of Masa CMS installed by checking the admin dashboard or version file
  2. 2. Determine which version branch you are on (7.2.x, 7.3.x, 7.4.x, or 7.5.x)
  3. 3. Upgrade to the corresponding fixed version: 7.2.10 for 7.2.x, 7.3.15 for 7.3.x, 7.4.10 for 7.4.x, or 7.5.3 for 7.5.x
  4. 4. Follow the standard Masa CMS upgrade procedure for your installation (backup database, test in staging first)
  5. 5. Verify the upgrade was successful and confirm anti-CSRF token validation is now enforced for the cTrash.empty function

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40309 — 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-40309 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