CVE-2026-40174: MasaCMS · Cross-Site Request Forgery (CSRF)
Affects MasaCMSSource GCVE Database
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
- 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:L/VI:H/VA:N/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 6 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| MasaCMS MasaCMS | Affected
| Fixed in
|
Description
Masa CMS is a content management system forked from Mura CMS. In versions 7.5.2 and earlier, the cUsers.updateAddress function does not properly validate anti-CSRF tokens for user address management operations. An attacker can induce a logged-in administrator to submit a forged request that adds, modifies, or deletes user address records, including email addresses and phone numbers. This can be used to alter contact information, redirect organizational communications, and corrupt address data in the user directory. 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, or deploy filtering rules to block forged requests to the affected endpoint