CVE-2026-40326
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 · uneditedMasa CMS is a content management system forked from Mura CMS. In versions 7.5.2 and earlier, the createBundle method in `csettings.cfc` does not properly validate anti-CSRF tokens for site bundle creation requests. An attacker can craft a malicious webpage or link that, when visited by a logged-in administrator, triggers the silent creation of a comprehensive site bundle. This bundle is saved to a predictable, publicly accessible web directory. An unauthenticated attacker can then retrieve the bundle and obtain site content, user account data, password hashes, form submissions, email lists, plugins, and configuration data. This issue has been fixed in versions 7.2.10, 7.3.15, 7.4.10, and 7.5.3. As a workaround, remove unexpected bundle files from public directories, restrict access to the affected endpoint, and limit exposure of administrative sessions.
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 confidenceMasa CMS versions 7.5.2 and earlier have a CSRF vulnerability in the createBundle method of csettings.cfc that allows attackers to trick authenticated administrators into silently creating a site bundle. This bundle is saved to a predictable, publicly accessible web directory, allowing unauthenticated attackers to download it and obtain sensitive data including password hashes, user accounts, configuration, and plugin data.
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:N/VA:N/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Masa CMS installationLook for Masa CMS in your web root - check for admin directories (typically /admin or /masa-admin), or look for the Application.cfc file with Masa CMS markers.Affected if Masa CMS is present in the environment
-
Identify installed Masa CMS versionAccess the admin dashboard and look for version information in the system settings or about page, or check any version.txt/version.cfm file in the installation root.Affected if Version is 7.5.2 or earlier, or cannot be determined and is assumed to be an unpatched release
-
Locate the vulnerable csettings.cfc componentSearch for csettings.cfc in the application directory, typically found in the admin or core modules folder.Affected if The file exists and is accessible without explicit CSRF protection checks in the code
-
Audit web-accessible directories for bundle filesSearch the web root for files with .bundle, .zip, or similar bundle extensions, particularly in publicly accessible paths. Check for files named with patterns like sitebundle, backup, or export.Affected if Any bundle files exist in web-public directories that should not be publicly accessible
-
Check for unexpected administrative bundle creation logsReview server and application logs for entries related to createBundle method execution, especially if initiated from unexpected IP addresses or times.Affected if Bundle creation events exist that were not explicitly authorized by administrators
A user is affected if Masa CMS version 7.5.2 or earlier is installed and either the csettings.cfc component is present or bundle files exist in web-accessible directories.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to patched versions (7.2.10, 7.3.15, 7.4.10, or 7.5.3) which implement proper anti-CSRF token validation. As immediate workarounds, remove any existing bundle files from public directories, restrict access to the bundle creation endpoint, and ensure administrative sessions have short timeouts.
7.5.3 (or 7.4.10 / 7.3.15 / 7.2.10 depending on your current branch)
- 1. Identify the currently installed Masa CMS version by checking the admin dashboard or version file
- 2. Determine which release branch you are on (7.2.x, 7.3.x, 7.4.x, or 7.5.x)
- 3. If on 7.5.x branch: upgrade to version 7.5.3 or later
- 4. If on 7.4.x branch: upgrade to version 7.4.10 or later
- 5. If on 7.3.x branch: upgrade to version 7.3.15 or later
- 6. If on 7.2.x branch: upgrade to version 7.2.10 or later
- 7. After upgrade, verify the anti-CSRF token validation is now enforced in the createBundle method in csettings.cfc
- 8. As an additional hardening measure, audit the web directory for any unexpectedly created bundle files and remove them if found
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,888.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40326 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-40326 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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