{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-55041 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-55041 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-55041 is a high-severity vulnerability in n/a, published on 18 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-55041 and fix it if it is affected.\n\nWhat it is: CVE-2025-55041 is a high-severity vulnerability in n/a, published on 18 Mar 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-55041 in the wild and no public exploit code.\n\nAffected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-55041/ (Markdown: https://insights.sbomify.com/CVE-2025-55041/index.md)","id":"CVE-2025-55041","markdown":"https://insights.sbomify.com/CVE-2025-55041/index.md","name":"CVE-2025-55041","record":{"aliases":["GHSA-cp9h-h8x8-m9h6"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"MuraCMS","requires_auth":"low_privilege","summary":"Attackers can exploit a CSRF flaw in MuraCMS to add users to privileged groups, resulting in privilege escalation.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mura_cms","vendor":"murasoftware"}],"cvss":{"score":8,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-55041","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2025-55043"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2025-55040"},"products":["n/a"],"published":"2026-03-18","related":[{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-67829","kev_date_added":null,"published":"2026-03-18"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2025-67830","kev_date_added":null,"published":"2026-03-18"},{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2022-47003","kev_date_added":null,"published":"2023-02-01"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-55040","kev_date_added":null,"published":"2026-03-18"},{"cvss_score":8.8,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-55044","kev_date_added":null,"published":"2026-03-18"},{"cvss_score":8.1,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-55046","kev_date_added":null,"published":"2026-03-18"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-03-19","vendors":["n/a"]},"summary":"Attackers can exploit a CSRF flaw in MuraCMS to add users to privileged groups, resulting in privilege escalation.","url":"https://insights.sbomify.com/CVE-2025-55041/"}