{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-55045 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-55045 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-55045 is a high-severity vulnerability in n/a, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-55045 and fix it if it is affected.\n\nWhat it is: CVE-2025-55045 is a high-severity vulnerability in n/a, published on 18 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-55045 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-55045/ (Markdown: https://insights.sbomify.com/CVE-2025-55045/index.md)","id":"CVE-2025-55045","markdown":"https://insights.sbomify.com/CVE-2025-55045/index.md","name":"CVE-2025-55045","record":{"aliases":["GHSA-6r2v-hf4m-fxxv"],"analysis":{"component_type":"web_application","fix_type":"patch","impacts":["data_modify","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"MuraCMS","requires_auth":"none","summary":"Attackers can manipulate user address data via CSRF when an authenticated administrator visits a malicious webpage, compromising data integrity.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"mura_cms","vendor":"murasoftware"}],"cvss":{"score":7.1,"severity":"high","source":"cisa-adp","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"The update address CSRF vulnerability in MuraCMS through 10.1.10 allows attackers to manipulate user address information through CSRF. The vulnerable cUsers.updateAddress function lacks CSRF token validation, enabling malicious websites to forge requests that add, modify, or delete user addresses when an authenticated administrator visits a crafted webpage. Successful exploitation of the update address CSRF vulnerability results in unauthorized manipulation of user address information within the MuraCMS system, potentially compromising user data integrity and organizational communications. When an authenticated administrator visits a malicious webpage containing the CSRF exploit, their browser automatically submits a hidden form that can add malicious addresses with attacker-controlled email addresses and phone numbers, update existing addresses to redirect communications to attacker-controlled locations or deleted legitimate address records to disrupt business operations. This can lead to misdirected sensitive communications, compromise of user privacy through injection of attacker contact information, disruption of legitimate business correspondence, and potential social engineering attacks via the corrupted address data.","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-55045","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":3,"next":{"headline":"Cross-site request forgery in n/a","id":"CVE-2025-55046"},"packages":[],"prev":{"headline":"Cross-site request forgery in n/a","id":"CVE-2025-55044"},"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"},{"cvss_score":8,"headline":"Cross-site request forgery in n/a","id":"CVE-2025-55041","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":"partial"},"state":"PUBLISHED","updated":"2026-03-19","vendors":["n/a"]},"summary":"Attackers can manipulate user address data via CSRF when an authenticated administrator visits a malicious webpage, compromising data integrity.","url":"https://insights.sbomify.com/CVE-2025-55045/"}