dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-40329

CRITICAL · 9.3 CVSS v4.0 Published 2026-05-05
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Masa CMS is an open source content management system. In versions 7.5.2 and earlier, a SQL injection vulnerability exists in the beanFeed.cfc component within the getQuery function's processing of the sortBy parameter. The application fails to properly sanitize or parameterize this input before incorporating it into dynamic SQL statements. An unauthenticated remote attacker can execute arbitrary SQL commands against the database, potentially gaining access to sensitive data, modifying or deleting records, or escalating privileges to administrative control. This issue has been fixed in versions 7.2.10, 7.3.15, 7.4.10, and 7.5.3. As a workaround, configure WAF rules to block malicious SQL patterns in the sortBy parameter sent to beanFeed.cfc.

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 confidence

A SQL injection vulnerability exists in Masa CMS's beanFeed.cfc component, specifically in the getQuery function's processing of the sortBy parameter. The application directly incorporates the unsanitized sortBy parameter into dynamic SQL queries without proper parameterization, allowing unauthenticated remote attackers to inject and execute arbitrary SQL commands.

MitigationUpgrade Masa CMS to version 7.2.10, 7.3.15, 7.4.10, or 7.5.3 or later. Alternatively, deploy WAF rules to block malicious SQL patterns in the sortBy parameter.

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
None
Scope
X

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Masa CMS installation
    Locate the beanFeed.cfc file in the web root or application directory (commonly in /components/ or /cfc/ folder). If the file exists, Masa CMS is present.
    Affected if beanFeed.cfc file is found on the server
  2. Identify Masa CMS version
    Check for a version file or configuration (often in /Application.cfc, /config/application.cfc, or a /version.cfm file). Compare the installed version against the known fixed versions: 7.2.10, 7.3.15, 7.4.10, 7.5.3.
    Affected if Installed version is lower than 7.2.10, 7.3.15, 7.4.10, or 7.5.3 (or version cannot be determined)
  3. Verify beanFeed.cfc component is accessible
    Test HTTP access to the beanFeed.cfc endpoint via the web server (e.g., GET request to /components/beanFeed.cfc or the path where beanFeed.cfc is located).
    Affected if The component responds to HTTP requests without authentication
  4. Confirm getQuery function exposure
    Examine the beanFeed.cfc source code to locate the getQuery function. Verify it accepts a sortBy parameter without sanitization (search for 'sortBy' variable usage in SQL queries without cfqueryparam or sanitization functions).
    Affected if The getQuery function uses the sortBy parameter directly in SQL without input validation or parameterized queries

A system is affected if Masa CMS is installed with a version below 7.2.10/7.3.15/7.4.10/7.5.3 AND the beanFeed.cfc component with the vulnerable getQuery function is accessible via HTTP.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Masa CMS to version 7.2.10, 7.3.15, 7.4.10, or 7.5.3 or later. Alternatively, deploy WAF rules to block malicious SQL patterns in the sortBy parameter.

Recommended fix High confidence

Masa CMS 7.5.3 (or the latest available version from the 7.2.x, 7.3.x, or 4.x branches)

  1. 1. Identify the current Masa CMS version running in the environment
  2. 2. Determine which release branch is in use (7.2.x, 7.3.x, 7.4.x, or 7.5.x)
  3. 3. Download the appropriate fixed version: 7.2.10, 7.3.15, 7.4.10, or 7.5.3 from the official Masa CMS repository
  4. 4. Review release notes for the target version to understand any changes
  5. 5. Create a full backup of the database and application files
  6. 6. Test the upgrade in a staging environment before deploying to production
  7. 7. Deploy the upgraded version to production
  8. 8. Verify the beanFeed.cfc component is updated and the sortBy parameter is now properly sanitized
Caveat Review release notes for potential breaking changes between current version and target fixed version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
8.0 hours of engineering $1,370
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,192.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40329 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-40329 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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