dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-40330

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.2.0 through 7.2.9, 7.3.0 through 7.3.14, 7.4.0 through 7.4.9, and 7.5.0 through 7.5.2, a SQL injection vulnerability exists in the beanFeed.cfc component within the getQuery function's handling of the sortDirection parameter. The parameter value is concatenated directly into SQL queries without sanitization or parameterization. An unauthenticated remote attacker can exploit this to extract sensitive information, modify or delete database records, or potentially achieve remote code execution on the underlying database server. This issue has been fixed in versions 7.2.10, 7.3.15, 7.4.10, and 7.5.3. As a workaround, use a WAF to block or restrict access to the beanFeed.cfc component, or deploy rules to detect SQL injection patterns targeting the sortDirection parameter.

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

SQL injection vulnerability in Masa CMS beanFeed.cfc's getQuery function allows unauthenticated remote attackers to inject malicious SQL via the sortDirection parameter, which is directly concatenated into queries without parameterization or sanitization, enabling data exfiltration, modification, deletion, or potential RCE on the underlying database server.

MitigationUpgrade to patched versions (7.2.10, 7.3.15, 7.4.10, or 7.5.3) to implement proper query parameterization; alternatively, deploy WAF rules to block SQL injection patterns targeting the sortDirection 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. Identify Masa CMS installation and version
    Locate the version file or admin interface. Common locations: /admin or check for version.json or Application.cfc in the root. The version may also appear in the admin dashboard footer.
    Affected if The installed version is 7.2.x before 7.2.10, 7.3.x before 7.3.15, 7.4.x before 7.4.10, or 7.5.x before 7.5.3
  2. Locate beanFeed.cfc component
    Search the webroot for beanFeed.cfc file. Common paths include /modules/v1/external/beanFeed.cfc or /core/modules/v1/external/beanFeed.cfc.
    Affected if beanFeed.cfc exists in the application directory and is web-accessible
  3. Verify beanFeed.cfc is accessible via HTTP
    Attempt an HTTP request to the beanFeed.cfc endpoint (e.g., GET /modules/v1/external/beanFeed.cfc?method=getQuery&sortDirection=test) and confirm the server responds.
    Affected if The component returns a response rather than a 404 or 403 error, indicating it is exposed
  4. Inspect the getQuery function for vulnerable parameter handling
    Review the beanFeed.cfc source code and locate the getQuery function. Search for direct concatenation of the sortDirection parameter into SQL queries without cfqueryparam usage.
    Affected if The sortDirection parameter is directly concatenated into SQL (e.g., 'ORDER BY #sortDirection#' or similar) without sanitization or parameterization

A user is affected if Masa CMS is installed with a version prior to 7.2.10, 7.3.15, 7.4.10, or 7.5.3 AND the beanFeed.cfc component is accessible and contains the vulnerable unsanitized sortDirection parameter in the getQuery function.

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 to patched versions (7.2.10, 7.3.15, 7.4.10, or 7.5.3) to implement proper query parameterization; alternatively, deploy WAF rules to block SQL injection patterns targeting the sortDirection parameter.

Recommended fix High confidence

Upgrade to 7.2.10, 7.3.15, 7.4.10, or 7.5.3 depending on current branch (7.2.x→7.2.10, 7.3.x→7.3.15, 7.4.x→7.4.10, 7.5.x→7.5.3)

  1. 1. Identify the currently installed Masa CMS version by checking the administration interface or version file
  2. 2. Based on the current version, determine the appropriate upgrade target: if on 7.2.x upgrade to 7.2.10, if on 7.3.x upgrade to 7.3.15, if on 7.4.x upgrade to 7.4.10, if on 7.5.x upgrade to 7.5.3
  3. 3. Back up the entire Masa CMS installation including database before proceeding with upgrade
  4. 4. Download the updated Masa CMS release from the official GitHub repository matching your target version
  5. 5. Replace the existing installation files with the new version files, preserving configuration and content
  6. 6. Test the upgrade in a staging environment before deploying to production
  7. 7. Verify that the beanFeed.cfc component has been updated by checking the sortDirection parameter handling in the getQuery function
  8. 8. Deploy to production after successful validation
Caveat Review release notes for minor changes between versions; standard upgrade precautions apply

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

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-40330 — 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-40330 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