Skip to main content
VulnerabilityPublished

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

Affects MasaCMSSource GCVE Database

0

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

Data as of 27 Oct 2026, 00:07 UTC

CVSS 4.0 base score
8.7High
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:H/VA:L/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 `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.

References

Community reviews

Loading reviews…