{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39339 exists.","fix":"No fix has been published for CVE-2026-39339 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-39339 is a critical authentication bypass vulnerability in Churchcrm Churchcrm, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim."},"fix_prompt":"Check this codebase for CVE-2026-39339 and fix it if it is affected.\n\nWhat it is: CVE-2026-39339 is a critical authentication bypass vulnerability in Churchcrm Churchcrm, published on 7 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-39339 exists.\n\nAffected product: Churchcrm Churchcrm. 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-39339/ (Markdown: https://insights.sbomify.com/CVE-2026-39339/index.md)","id":"CVE-2026-39339","markdown":"https://insights.sbomify.com/CVE-2026-39339/index.md","name":"CVE-2026-39339","record":{"aliases":["GHSA-v3p2-mx78-pxhc"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["data_read","security_bypass"],"network_reachable":"yes","non_default_config":false,"product_category":"ChurchCRM","requires_auth":"none","summary":"Unauthenticated attackers can bypass API authentication in ChurchCRM to access protected endpoints and expose sensitive member data.","user_interaction":"not_required","vuln_class":"auth_bypass"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"churchcrm","vendor":"churchcrm"}],"cvss":{"score":9.1,"severity":"critical","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-284","name":"Improper Access Control"}],"description":"ChurchCRM is an open-source church management system. Prior to 7.1.0, a  critical authentication bypass vulnerability in ChurchCRM's API middleware (ChurchCRM/Slim/Middleware/AuthMiddleware.php) allows unauthenticated attackers to access all protected API endpoints by including \"api/public\" anywhere in the request URL, leading to complete exposure of church member data and system information. This vulnerability is fixed in 7.1.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":1,"refs":[{"date":null,"kind":"nuclei","ref":"http/cves/2026/CVE-2026-39339.yaml","stars":null,"title":"ChurchCRM - API Authentication Bypass via URL Injection"}],"tier":"weaponised"},"has_fix":false,"headline":"ChurchCRM has an API Authentication Bypass","id":"CVE-2026-39339","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"churchcrm:churchcrm","products":["churchcrm:churchcrm"],"type":"auth_bypass","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"ChurchCRM has a SQL Injection in PropertyTypeEditor.php via Incorrect Sanitizer Substitution","id":"CVE-2026-39340"},"packages":[],"prev":{"headline":"ChurchCRM has Blind XSS via Global Search – Administrative Cookie Session Exfiltration","id":"CVE-2026-39338"},"products":["CRM"],"published":"2026-04-07","related":[{"cvss_score":10,"headline":"ChurchCRM Affected by Unauthenticated RCE in Install Wizard","id":"CVE-2026-39337","kev_date_added":null,"published":"2026-04-07"},{"cvss_score":10,"headline":"ChurchCRM has unauthenticated RCE in its Install Wizard","id":"CVE-2025-62521","kev_date_added":null,"published":"2025-12-17"},{"cvss_score":10,"headline":"ChurchCRM discloses database information on error message","id":"CVE-2025-68110","kev_date_added":null,"published":"2025-12-17"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-53438","kev_date_added":null,"published":"2024-11-22"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-25894","kev_date_added":null,"published":"2024-02-21"},{"cvss_score":9.8,"headline":"SQL injection in n/a","id":"CVE-2024-25897","kev_date_added":null,"published":"2024-02-21"},{"cvss_score":9.6,"headline":"ChurchCRM has SQL injection in EditEventAttendees.php","id":"CVE-2025-68112","kev_date_added":null,"published":"2025-12-17"}],"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)"},{"class":"attribution","licence":"MIT","name":"Nuclei templates"}],"ssvc":{"automatable":"yes","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-07","vendors":["ChurchCRM"]},"summary":"Unauthenticated attackers can bypass API authentication in ChurchCRM to access protected endpoints and expose sensitive member data.","url":"https://insights.sbomify.com/CVE-2026-39339/"}