VulnerabilityPublished 18 Mar 2026Updated 19 Mar 2026

CVE-2025-55043: MuraCMS · CSRF

Source CVE Database V5

Not known to be exploited · CVSS 6.5 Medium · fixed in 10.1.11 : update MuraCMS when convenient.

Data as of 26 Oct 2026, 17:16 UTC

CVSS 3.1 base score

6.5Medium

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

EPSS: 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Affects: MuraCMS through 10.1.10
Patch: Available – fixed in 10.1.11

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

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

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: Required: Successful exploitation of this vulnerability requires a user to take some action before the vulnerability can be exploited.
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: None: There is no loss of integrity within the impacted component.
Availability: None: There is no impact to availability within the impacted component.

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

Implement robust anti-CSRF tokens on all state-changing endpoints, especially the bundle creation functionality, to ensure requests originate from legitimate sources.
Restrict access permissions on directories where bundles are stored to prevent public access; consider moving bundle storage outside the web root or applying strict access controls via web server configuration.
Monitor logs and audit trails for unusual bundle creation activity or access patterns indicative of exploitation attempts.
Educate administrators about phishing and social engineering risks to reduce the likelihood of clicking malicious links.
Apply the principle of least privilege for administrator accounts and consider multi-factor authentication to reduce risk from compromised credentials.
Regularly update MuraCMS to the latest versions once patches addressing this vulnerability are released.
Employ web application firewalls (WAFs) to detect and block suspicious CSRF attack patterns targeting the bundle creation endpoint.
Conduct security assessments and penetration testing focused on CSRF and sensitive data exposure vectors within the CMS environment.

Description

CVE-2025-55043 is a Cross-Site Request Forgery (CSRF) vulnerability in MuraCMS versions through 10.1.10 affecting the bundle creation functionality. It allows unauthenticated attackers to trick administrators into creating site bundles containing sensitive data, which are saved to publicly accessible directories. This enables attackers to exfiltrate critical information such as user accounts, password hashes, form submissions, email lists, plugins, and site content without the administrator's knowledge. The attack requires user interaction (administrator visiting a malicious link) but no authentication by the attacker. The vulnerability has a CVSS score of 6.5 (medium severity) and does not impact integrity or availability but results in high confidentiality loss. No known exploits are currently reported in the wild. Organizations using vulnerable MuraCMS versions should implement strict CSRF protections, restrict access to bundle files, and monitor for suspicious bundle creation activity.

Impact

This vulnerability can lead to complete data exfiltration from affected MuraCMS installations, exposing highly sensitive information such as user accounts, password hashes, and private site content. Organizations relying on MuraCMS for website management risk severe confidentiality breaches that could facilitate further attacks, including credential stuffing, phishing, or targeted exploitation using stolen data. Since the attack does not require attacker authentication and can be executed remotely via social engineering, the threat surface is broad. The silent nature of the attack means administrators may remain unaware of the breach, delaying detection and response. This can result in prolonged exposure and increased damage. The vulnerability does not affect system integrity or availability directly but compromises trust and confidentiality, potentially leading to reputational damage, regulatory penalties, and loss of customer trust.

Summary

CVE-2025-55043 is a CSRF vulnerability identified in MuraCMS, a popular content management system, affecting versions up to 10.1.10. The flaw resides in the createBundle method within the csettings.cfc component responsible for generating site bundles. An attacker can craft a malicious request that, when an authenticated administrator unknowingly executes (e.g., by clicking a link), forces the CMS to create and save a site bundle containing sensitive data. These bundles include user credentials, password hashes, form data, email lists, plugins, and other site content. Because the bundles are stored in publicly accessible web directories, attackers can download them directly without authentication. The vulnerability requires no privileges or authentication from the attacker and exploits the lack of CSRF protections on the bundle creation endpoint. The attack is silent, leaving administrators unaware of the data compromise. The CVSS vector indicates network attack vector, low attack complexity, no privileges required, but requires user interaction, with high confidentiality impact and no integrity or availability impact. Although no public exploits are known, the vulnerability poses a significant risk due to the sensitive nature of the exposed data and the ease of exploitation through social engineering. The vulnerability is classified under CWE-352 (Cross-Site Request Forgery).

CWE-352Cross-Site Request Forgery (CSRF) (opens in a new tab)
Compound weaknessLikelihood of exploit: MediumCWE Top 25 (2025): #3OWASP Top 10 A01:2025: Broken Access Control (opens in a new tab)
The web application does not, or cannot, sufficiently verify whether a request was intentionally provided by the user who sent the request, which could have originated from an unauthorized actor.
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.
Implementation
Ensure that the application is free of cross-site scripting issues (CWE-79), because most CSRF defenses can be bypassed using attacker-controlled script.
Architecture and Design
Generate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).
OWASP Cheat Sheets
REST Assessment (opens in a new tab)
REST Security (opens in a new tab)
Cross-Site Request Forgery Prevention (opens in a new tab)
Authorization Testing Automation (opens in a new tab)
Insecure Direct Object Reference Prevention (opens in a new tab)
OWASP ASVS 4.0.3
V13.2.3 (opens in a new tab)
V4.2.2 (opens in a new tab)
V13.3.2 (opens in a new tab)
Attack patterns
JSON Hijacking (aka JavaScript Hijacking) (opens in a new tab)
Cross-Domain Search Timing (opens in a new tab)
Cross Site Identification (opens in a new tab)
Cross Site Request Forgery (opens in a new tab)
From MITRE CWE, MITRE CAPEC and OWASP (Top 10, OpenCRE).

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Description

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

WeaknessesCWE-352

Technical details

References

Community reviews

Related threats