Vulnary
← back to the feed
Critical· 9.3official fix available

CVE-2026-40330

A critical SQL injection flaw exists in Masa CMS’s beanFeed.cfc component. The flaw allows an unauthenticated attacker to inject arbitrary SQL through the sortDirection parameter, potentially reading, modifying, or deleting database data and even executing code on the database server.

publishedMay 5, 2026
last modifiedJul 24, 2026
sourcesNVD
severity · cvss
9.3
critical · how bad it is
exploitation · epss
<1%
35th percentile · chance of exploitation in 30 days
(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →
auto-deletes from the system
counting…on Aug 25, 2026

An official fix is available, so this entry is kept for 30 days and then removed automatically.

01

Who is affected

Masa CMS versions 7.2.0‑7.2.9, 7.3.0‑7.3.14, 7.4.0‑7.4.9, and 7.5.0‑7.5.2. Site owners running these releases are at risk.

02

Real-world impact

An attacker could pull confidential data, alter or erase records, or run malicious commands on the database, compromising the integrity and confidentiality of the site’s information.

03

Why this severity

The CVSS score of 9.3 reflects the vulnerability’s high impact on confidentiality, integrity, and availability, combined with its low attack complexity, lack of required authentication, and no user interaction.

04

What to do about it

official fix available
recommended steps
  1. 01Upgrade Masa CMS to a fixed version (7.2.10 or later, 7.3.15 or later, 7.4.10 or later, or 7.5.3 or later).
  2. 02Restart the web server or application to apply the changes.
interim mitigations
  • Use a WAF to block or restrict access to the beanFeed.cfc component.
  • Deploy rules to detect SQL injection patterns targeting the sortDirection parameter.

NVD-referenced vendor advisory

05

Timeline

  1. May 5, 2026 · May 5, 2026
    Published
    Disclosed and added to the National Vulnerability Database.
  2. Jul 24, 2026 · 11d ago
    Advisory updated
    The NVD record was last revised.
  3. Jul 26, 2026 · 10d ago
    Official fix available
    A vendor patch or mitigation now exists — see the remediation steps above.
06

How it’s attacked

Attack vectorNetwork (remote)
Attack complexityLow
Attack requirementsNone
Privileges requiredNone
User interactionNone needed
Confidentiality impactHigh
Integrity impactHigh
Availability impactHigh
07

References & advisories

(ai-assisted) A model wrote this summary from the official data, so double-check it against the source before you act on it. Read the official advisory →