VulnerabilityPublished 18 Mar 2026Updated 19 Mar 2026

CVE-2025-67830: Mura CMS · CVE-2025-67830 is a critical SQL injection

Source CVE Database V5

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

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

9.8Critical

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

EPSS: 0.3% chance of exploitation in 30 days – higher than 26% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Affects: Mura CMS before 10.1.14
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

1. 2. If you cannot patch yet, implement Web Application Firewall (WAF) rules to detect and block SQL injection attempts targeting the beanFeed.cfc getQuery sortby parameter. 3. Conduct thorough input validation and sanitization on all user-supplied data, especially parameters used in database queries. 4. Restrict database user permissions to the minimum necessary, avoiding use of highly privileged accounts for web applications. 5. Monitor database logs and web server logs for unusual or suspicious query patterns indicative of SQL injection attempts. 6. Employ network segmentation to isolate critical systems and reduce the attack surface. 7. Educate development teams on secure coding practices to prevent similar vulnerabilities in the future. 8. Consider temporary disabling or restricting access to the vulnerable component if feasible until a patch is applied.

Description

CVE-2025-67830 is a critical SQL injection vulnerability in Mura CMS versions before 10.1.14, specifically in the beanFeed.cfc component's getQuery sortby parameter. This flaw allows unauthenticated remote attackers to execute arbitrary SQL commands, potentially leading to full database compromise, including data confidentiality, integrity, and availability impacts. The vulnerability requires no user interaction and can be exploited over the network, making it highly dangerous. Although no known exploits are currently reported in the wild, the high CVSS score of 9.8 indicates severe risk. Organizations using vulnerable Mura CMS versions should prioritize patching once available or apply immediate mitigations to prevent exploitation. Countries with significant Mura CMS usage and critical infrastructure relying on it are at higher risk.

Impact

The impact of CVE-2025-67830 is severe for organizations worldwide using vulnerable versions of Mura CMS. Exploitation can lead to complete compromise of the backend database, resulting in unauthorized disclosure of sensitive data, data tampering, or deletion. This can cause significant operational disruption, loss of customer trust, regulatory penalties, and financial damage. Since the vulnerability requires no authentication and can be exploited remotely, attackers can leverage it to gain persistent access or pivot to other internal systems. Critical sectors such as government, finance, healthcare, and e-commerce that rely on Mura CMS for content management are particularly at risk. The potential for widespread data breaches and service outages elevates the threat to a critical level, necessitating immediate attention from security teams.

Summary

CVE-2025-67830 is a critical SQL injection vulnerability identified in Mura CMS versions prior to 10.1.14, specifically within the beanFeed.cfc file's getQuery function, targeting the sortby parameter. This vulnerability arises from improper sanitization of user-supplied input, allowing attackers to inject malicious SQL code directly into database queries. The vulnerability is classified under CWE-89 (Improper Neutralization of Special Elements used in an SQL Command). Exploitation requires no authentication or user interaction and can be performed remotely over the network. Successful exploitation can lead to unauthorized data access, modification, or deletion, compromising confidentiality, integrity, and availability of the affected systems. The CVSS v3.1 base score of 9.8 reflects the critical nature of this vulnerability, with attack vector being network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), no user interaction (UI:N), and full impact on confidentiality (C:H), integrity (I:H), and availability (A:H). Although no public exploits have been reported yet, the vulnerability's characteristics make it a prime target for attackers once exploit code becomes available. The lack of a patch link suggests that a fix may still be pending or not publicly disclosed at the time of this report, emphasizing the need for vigilance and interim protective measures.

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:18 UTC

WeaknessesCWE-89

Technical details

References

Community reviews

Related threats