CVE-2026-40331
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 · uneditedMasa 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, the unauthenticated JSON API accepts an altTable parameter that is stored via the setAltTable() method without validation or sanitization. This value is injected directly into a SQL FROM clause within feedGateway.cfc. An unauthenticated attacker can pass an arbitrary subquery into the altTable parameter to read sensitive data from any table in the database in a single HTTP request, including administrative credentials and password reset tokens. This issue has been fixed in versions 7.2.10, 7.3.15, 7.4.10, and 7.5.3. As a workaround, apply validation to the setAltTable function in core/mura/content/feed/feedBean.cfc to restrict input to simple alphanumeric table names, or disable the JSON API if it is not required.
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 confidenceSQL injection in Masa CMS JSON API via unsanitized altTable parameter passed to setAltTable() method in feedGateway.cfc. The parameter value is directly injected into a SQL FROM clause without validation, allowing unauthenticated attackers to inject arbitrary subqueries and extract sensitive data including administrative credentials and password reset tokens.
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 checksWork through these to decide whether this CVE applies to you.
-
Check Masa CMS versionLocate the version file or admin dashboard that displays the installed Masa CMS version. Common locations include a version.cfm file, the admin about page, or the root index page.Affected if Version is 7.2.0-7.2.9, 7.3.0-7.3.14, 7.4.0-7.4.9, or 7.5.0-7.5.2
-
Verify JSON API is accessibleConfirm the JSON API endpoint is exposed and reachable without authentication. Try accessing the API endpoint (commonly /api/v1/ or /?muraJSONAPI=1) from an unauthenticated request.Affected if JSON API responds to unauthenticated requests
-
Inspect feedGateway.cfc for vulnerable setAltTable methodLocate the feedGateway.cfc file (typically in core/mura/content/feed/) and examine the setAltTable() method. Look for direct concatenation of the altTable parameter into SQL queries without sanitization.Affected if The setAltTable() method passes the altTable parameter directly into SQL FROM clauses without input validation
-
Check feedBean.cfc for input validation on altTableExamine core/mura/content/feed/feedBean.cfc to determine if the setAltTable() method or altTable parameter has input validation restricting values to alphanumeric table names only.Affected if No input validation exists on the altTable parameter, allowing arbitrary SQL injection payloads
If the installed Masa CMS version falls within 7.2.0-7.2.9, 7.3.0-7.3.14, 7.4.0-7.4.9, or 7.5.0-7.5.2 AND the JSON API is accessible without authentication AND the setAltTable() method lacks input validation, the environment is vulnerable to CVE-2026-40331.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade to patched versions (7.2.10, 7.3.15, 7.4.10, or 7.5.3) or implement input validation restricting the altTable parameter to simple alphanumeric table names only.
Masa CMS 7.2.10, 7.3.15, 7.4.10, or 7.5.3 (depending on your current major.minor version)
- Identify the currently installed Masa CMS version by checking the admin dashboard or configuration files
- Backup the entire Masa CMS installation and database before proceeding with any changes
- Upgrade to the appropriate fixed version based on your current version: 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
- Download the updated Masa CMS release from the official repository or distribution channel
- Deploy the upgrade following standard Masa CMS upgrade procedures, which typically involve replacing core files while preserving configuration and content
- Verify the upgrade was successful by checking the version number in the admin interface
- As an alternative workaround (if upgrade is not immediately feasible), edit core/mura/content/feed/feedBean.cfc and add validation to the setAltTable() method to restrict the altTable parameter to simple alphanumeric table names only, rejecting any input containing SQL keywords or special characters
- Alternatively, if the JSON API is not required, disable it entirely via configuration
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing8.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,896.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-40331 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-40331 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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