dbcve.org
Mura CmsApplication · Murasoftware

CVE-2025-67829

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-18
Fix available
A fix is available. Upgrade to 10.1.4 or later.
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
Mura before 10.1.14 allows beanFeed.cfc getQuery sortDirection SQL injection.

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 Mura CMS versions prior to 10.1.14. The vulnerability is located in the beanFeed.cfc component's getQuery method, specifically in the sortDirection parameter, which fails to properly sanitize user input before using it in SQL queries. An unauthenticated attacker could exploit this to inject arbitrary SQL commands, potentially leading to full database compromise.

MitigationUpgrade Mura CMS to version 10.1.14 or later to obtain the patched version that properly sanitizes the sortDirection parameter in beanFeed.cfc.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Mura CmsApplication
Affected:< 10.1.4

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
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 Mura CMS installation and version
    Locate the Mura CMS installation directory and check the version file (typically in /config/application.cfc or a version.cfc file within the Mura root or core directory). Look for a version identifier such as 'version', 'build', or 'release' metadata.
    Affected if The installed version is below 10.1.14 (e.g., 10.1.0, 10.0.x, 9.x, etc.)
  2. Locate beanFeed.cfc component
    Search the Mura CMS codebase for the file beanFeed.cfc. This is typically found in the /core/modules/v1/external/configBean/ directory or similar location under the Mura installation root.
    Affected if The beanFeed.cfc file exists in the installation, indicating the vulnerable component is present.
  3. Verify getQuery method handles sortDirection
    Open beanFeed.cfc and locate the getQuery method. Inspect how the sortDirection parameter is processed - specifically look for direct insertion into SQL query strings without visible sanitization functions (such as PreserveSingleQuotes, HTMLEditFormat, or parameterized queries).
    Affected if The getQuery method uses the sortDirection parameter directly in SQL concatenation without apparent input validation or escaping.
  4. Check unauthenticated access to beanFeed functionality
    Determine if the beanFeed.cfc component or its getQuery method is accessible to unauthenticated users. This typically involves checking the application's routing or URL patterns that invoke this component (e.g., /?mura=feed&type=beanfeed or similar endpoints).
    Affected if The beanFeed functionality is reachable without authentication, allowing unauthenticated attackers to control the sortDirection parameter.

A user is affected if running any Mura CMS version prior to 10.1.14 where beanFeed.cfc with the vulnerable getQuery method is accessible to unauthenticated users.

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
Upgrade available Upgrade to 10.1.4 or later
Fixed in 10.1.4
Interim mitigation

Upgrade Mura CMS to version 10.1.14 or later to obtain the patched version that properly sanitizes the sortDirection parameter in beanFeed.cfc.

Recommended fix High confidence

Mura Cms 10.1.14 or later

  1. 1. Backup your current Mura Cms installation and database before proceeding with any upgrade.
  2. 2. Download Mura Cms version 10.1.14 or later from the official Mura software repository (docs.murasoftware.com).
  3. 3. Follow the official Mura Cms upgrade instructions to apply the update.
  4. 4. Verify the upgrade was successful by checking the Mura Cms version in the admin dashboard.
  5. 5. Test the beanFeed.cfc functionality to confirm the SQL injection vulnerability is resolved.
  6. 6. Monitor application logs for any unusual database activity.
Caveat Review Mura release notes for any breaking changes between your current version and 10.1.14

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

Fix this in Mura Cms Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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