{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40484 exists.","fix":"No fix has been published for CVE-2026-40484 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-40484 is a critical vulnerability in ChurchCRM CRM, published on 17 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-40484 and fix it if it is affected.\n\nWhat it is: CVE-2026-40484 is a critical vulnerability in ChurchCRM CRM, published on 17 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40484 exists.\n\nAffected product: ChurchCRM CRM. 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-2026-40484/ (Markdown: https://insights.sbomify.com/CVE-2026-40484/index.md)","id":"CVE-2026-40484","markdown":"https://insights.sbomify.com/CVE-2026-40484/index.md","name":"CVE-2026-40484","record":{"aliases":["GHSA-2932-77f9-62fx"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["code_execution","privilege_escalation"],"network_reachable":"yes","non_default_config":false,"product_category":"ChurchCRM","requires_auth":"high_privilege","summary":"Authenticated administrators can upload malicious PHP files via the database restore function, leading to remote code execution on the server.","user_interaction":"not_required","vuln_class":"file_upload"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H","version":"3.1"},"cwes":[{"id":"CWE-552","name":"Files or Directories Accessible to External Parties"},{"id":"CWE-434","name":"Unrestricted Upload of File with Dangerous Type"},{"id":"CWE-269","name":"Improper Privilege Management"}],"description":"ChurchCRM is an open-source church management system. In versions prior to 7.2.0, the database backup restore functionality extracts uploaded archive contents and copies files from the Images/ directory into the web-accessible document root using recursiveCopyDirectory(), which performs no file extension filtering. An authenticated administrator can upload a crafted backup archive containing a PHP webshell inside the Images/ directory, which is then written to a publicly accessible path and executable via HTTP requests, resulting in remote code execution as the web server user. The restore endpoint also lacks CSRF token validation, enabling exploitation through cross-site request forgery targeting an authenticated administrator. This issue has been fixed in version 7.2.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"weaponised"},"has_fix":false,"headline":"ChurchCRM: Authenticated Remote Code Execution via Unrestricted PHP File Write in Database Restore Function","id":"CVE-2026-40484","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"file_upload","year":"2026"},"n_packages":0,"n_references":3,"next":{"headline":"ChurchCRM: Username Enumeration via Differential Response in Public Login API","id":"CVE-2026-40485"},"packages":[],"prev":{"headline":"ChurchCRM: Stored XSS in PledgeEditor.php via Donation Comment Field","id":"CVE-2026-40483"},"products":["CRM"],"published":"2026-04-17","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-20","vendors":["ChurchCRM"]},"summary":"Authenticated administrators can upload malicious PHP files via the database restore function, leading to remote code execution on the server.","url":"https://insights.sbomify.com/CVE-2026-40484/"}