Skip to main content
VulnerabilityPublished

CVE-2026-40326: MasaCMS · Cross-Site Request Forgery (CSRF)

Affects MasaCMSSource GCVE Database

0

Not known to be exploited · CVSS 7.1 High · fixed in 7.5.3 : patch MasaCMS soon.

Data as of 27 Oct 2026, 00:07 UTC

CVSS 4.0 base score
7.1High
How severe the flaw is on the 0–10 CVSS scale.
Patch
Available – fixed in 7.5.3, 7.4.10, 7.3.15 +1
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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 May 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Upgrade MasaCMS to 7.5.3, 7.4.10, 7.3.15 or 7.2.10.

Affected software

ProductAffectedFixed in
MasaCMS MasaCMSAffected
  • <7.2.10
  • >=7.3.0 <7.3.15
  • >=7.4.0 <7.4.10
  • >=7.5.0 <7.5.3
Fixed in
  • 7.2.10
  • 7.3.15
  • 7.4.10
  • 7.5.3

Description

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

References

Community reviews

Loading reviews…