dbcve.org
Mura CmsApplication · Murasoftware

CVE-2025-55041

HIGH · 8.0 CVSS v3.1 Published 2026-03-18
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable

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
MuraCMS through 10.1.10 contains a CSRF vulnerability in the Add To Group functionality for user management (cUsers.cfc addToGroup method) that allows attackers to escalate privileges by adding any user to any group without proper authorization checks. The vulnerable function lacks CSRF token validation and directly processes user-supplied userId and groupId parameters via getUserManager().createUserInGorup(), enabling malicious websites to forge requests that automatically execute when an authenticated administrator visits a crafted page. Adding a user to the Super Admins group (s2 user) is not possible. Successful exploitation results in the attacker gaining privilege escalation both horizontally to other groups and vertically to the admin group. Escalation to the s2 User group is not possible.

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

MuraCMS through 10.1.10 contains a CSRF vulnerability in the user management component (cUsers.cfc addToGroup method). The function lacks CSRF token validation and directly processes user-supplied userId and groupId parameters via getUserManager().createUserInGroup(). Attackers can craft malicious pages that, when visited by an authenticated administrator, automatically add specified users to specified groups without proper authorization, enabling horizontal privilege escalation to other groups and vertical escalation to admin group (Super Admins/s2 group is excluded).

MitigationImplement CSRF token validation on the addToGroup method and add proper authorization checks to ensure the requesting user has permission to modify group memberships.

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:all versions

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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 MuraCMS installation
    Look for MuraCMS files in the web root. Check for existence of files such as /config/application.cfc, /core/modules/v1/external/configurator.cfm, or /requirements/mura/user/userDAO.cfc which are typical of MuraCMS installations.
    Affected if MuraCMS is not present on the server - the CVE only applies to MuraCMS installations.
  2. Determine the installed MuraCMS version
    Check the version file or configuration. Common locations include a version.cfm file in the root, the application.cfc in the config directory, or look for a 'version' property in /core/modules/v1/external/configurator.cfm.
    Affected if The installed version is any version through 10.1.10 (the CVE states all versions through 10.1.10 are affected). Versions after 10.1.10 may have fixes but this cannot be confirmed from the provided data.
  3. Locate the cUsers.cfc file
    Search for the cUsers.cfc component file in the MuraCMS installation, typically found under /core/modules/v1/external/handlers/ or similar paths in the MuraCMS structure.
    Affected if The cUsers.cfc file does not exist - the vulnerable component is not present.
  4. Check addToGroup method for CSRF token validation
    Examine the addToGroup method in cUsers.cfc. Search for CSRF token validation logic such as 'csrfTokenVerify', 'verifyCSRFToken', or similar CSRF protection function calls within the method.
    Affected if The addToGroup method exists but lacks CSRF token validation - the method directly processes userId and groupId parameters without verifying a CSRF token, which is the vulnerable condition.
  5. Verify getUserManager().createUserInGroup is called
    In cUsers.cfc addToGroup method, confirm that it directly calls getUserManager().createUserInGroup() with user-supplied parameters (userId and groupId) without authorization checks.
    Affected if The method directly calls getUserManager().createUserInGroup() with userId and groupId parameters from the request without validating the caller's permissions - this is the vulnerable code path.

The environment is affected if MuraCMS is installed, the version is through 10.1.10, and the cUsers.cfc addToGroup method does not implement CSRF token validation before processing userId and groupId parameters.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement CSRF token validation on the addToGroup method and add proper authorization checks to ensure the requesting user has permission to modify group memberships.

Fix this in Mura Cms Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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