VulnerabilityPublished 18 Mar 2026Updated 19 Mar 2026

CVE-2025-67829: SQL Injection

Source CVE Database V5

Not known to be exploited · CVSS 9.8 Critical · fixed in 10.1.14 : patch affected systems as a priority.

Data as of 26 Oct 2026, 12:55 UTC

CVSS 3.1 base score

9.8Critical

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 19% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch: Available – fixed in 10.1.14

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

Attack Vector: Network
Attack Complexity: Low
Privileges Required: None
User Interaction: None
Scope: Unchanged
Confidentiality: High
Integrity: High
Availability: High

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable component is bound to the network stack and the set of possible attackers extends beyond the other options listed, up to and including the entire Internet. Such a vulnerability is often termed 'remotely exploitable' and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: Specialized access conditions or extenuating circumstances do not exist. An attacker can expect repeatable success against the vulnerable component.
Privileges Required: None: The attacker is unauthorized prior to attack, and therefore does not require any access to settings or files to carry out an attack.
User Interaction: None: The vulnerable system can be exploited without any interaction from any user.
Scope: Unchanged: An exploited vulnerability can only affect resources managed by the same security authority. In this case, the vulnerable component and the impacted component are either the same, or both are managed by the same security authority.
Confidentiality: High: There is total loss of confidentiality, resulting in all resources within the impacted component being divulged to the attacker. Alternatively, access to only some restricted information is obtained, but the disclosed information presents a direct, serious impact.
Integrity: High: There is a total loss of integrity, or a complete loss of protection. For example, the attacker is able to modify any/all files protected by the impacted component. Alternatively, only some files can be modified, but malicious modification would present a direct, serious consequence to the impacted component.
Availability: High: There is total loss of availability, resulting in the attacker being able to fully deny access to resources in the impacted component; this loss is either sustained (while the attacker continues to deliver the attack) or persistent (the condition persists even after the attack has completed). Alternatively, the attacker has the ability to deny some availability, but the loss of availability presents a direct, serious consequence to the impacted component (e.g., the attacker cannot disrupt existing connections, but can prevent new connections; the attacker can repeatedly exploit a vulnerability that, in each instance of a successful attack, leaks a only small amount of memory, but after repeated exploitation causes a service to become completely unavailable).

Definitions: FIRST CVSS v3.1 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 18 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponised: Public exploit code exists in Metasploit or Exploit-DB, or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

AI-suggested

To mitigate CVE-2025-67829, organizations should immediately upgrade Mura CMS to version 10.1.14 or later once available, as this version addresses the SQL injection flaw. If you cannot patch yet, implement strict input validation and sanitization on the sortDirection parameter within beanFeed.cfc or at the web application firewall (WAF) level to block malicious SQL payloads. Employ parameterized queries or prepared statements in the application code to prevent injection attacks. Deploy a WAF with custom rules to detect and block SQL injection attempts targeting this vulnerability. Conduct thorough code reviews and penetration testing focused on SQL injection vectors in the CMS. Monitor logs for unusual database query patterns or errors indicative of attempted exploitation. Restrict database user permissions to the minimum necessary to limit the impact of a potential injection attack. Additionally, isolate the CMS environment from critical internal networks to reduce lateral movement risks. Maintain regular backups of the CMS database and files to enable rapid recovery in case of compromise.

Description

CVE-2025-67829 is a critical SQL injection vulnerability affecting Mura CMS versions prior to 10.1.14. The flaw exists in the beanFeed.cfc component's getQuery function, which improperly handles the sortDirection parameter, allowing an attacker to inject malicious SQL code. This vulnerability requires no authentication or user interaction and can be exploited remotely over the network. Successful exploitation can lead to full compromise of the affected system, including unauthorized data disclosure, data modification, and potential system availability disruption. Although no known exploits are currently in the wild, the high CVSS score of 9.8 indicates a severe risk. Organizations using vulnerable Mura CMS versions should prioritize patching or applying mitigations immediately to prevent exploitation.

Impact

The impact of CVE-2025-67829 on organizations worldwide is substantial. Exploitation can result in complete compromise of the affected Mura CMS installations, leading to unauthorized disclosure of sensitive data, including user information, credentials, and proprietary content. Attackers can also modify or delete data, undermining data integrity and potentially disrupting business operations. The vulnerability can be leveraged to execute arbitrary SQL commands, which may allow attackers to escalate privileges, pivot within internal networks, or deploy further malware. Given that Mura CMS is used by various enterprises, government agencies, and educational institutions, the breach of such systems could lead to reputational damage, regulatory penalties, and financial losses. The ease of exploitation without authentication or user interaction increases the likelihood of widespread attacks, especially targeting publicly accessible web servers. Organizations that fail to address this vulnerability risk becoming victims of data breaches, service outages, and long-term operational disruptions.

Summary

CVE-2025-67829 is a critical SQL injection vulnerability identified in Mura CMS versions before 10.1.14. The vulnerability resides in the beanFeed.cfc file, specifically within the getQuery function, which processes the sortDirection parameter without proper input validation or sanitization. This improper handling allows an attacker to inject arbitrary SQL commands into the backend database query. The vulnerability is remotely exploitable without requiring authentication or user interaction, making it highly accessible to attackers. Exploiting this flaw can lead to severe consequences including unauthorized access to sensitive data, data manipulation, and potential denial of service by corrupting or deleting database contents. The CVSS v3.1 base score is 9.8, reflecting the vulnerability's critical nature with network attack vector, low attack complexity, no privileges required, and no user interaction needed. Although no public exploits have been reported yet, the vulnerability's characteristics make it a prime target for attackers once exploit code becomes available. This vulnerability is categorized under CWE-89, which corresponds to SQL injection flaws, a well-known and dangerous class of vulnerabilities that have historically led to significant breaches.

CWE-89Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') (opens in a new tab)
Base weaknessLikelihood of exploit: HighCWE Top 25 (2025): #2OWASP Top 10 A05:2025: Injection (opens in a new tab)
The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data.
Architecture and Design · Libraries or Frameworks
Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.
Architecture and Design · Parameterization
If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.
Architecture and Design · Operation · Environment Hardening
Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment.
OWASP Cheat Sheets
Query Parameterization (opens in a new tab)
Unvalidated Redirects and Forwards (opens in a new tab)
XML Security (opens in a new tab)
XML External Entity Prevention (opens in a new tab)
File Upload (opens in a new tab)
OWASP ASVS 4.0.3
V5.3.4 (opens in a new tab)
V5.3.5 (opens in a new tab)
V1.5.1 (opens in a new tab)
Attack patterns
Command Line Execution through SQL Injection (opens in a new tab)
Object Relational Mapping Injection (opens in a new tab)
SQL Injection through SOAP Parameter Tampering (opens in a new tab)
Expanding Control over the Operating System from the Database (opens in a new tab)
SQL Injection (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

docs.murasoftware.com/v10/release-notes/ (opens in a new tab)

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

AI analysisMachine-generated, updated 26 Mar 2026, 01:17 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats