{"answers":{"affected":"It affects 1 product.","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35576 exists.","fix":"No fix has been published for CVE-2026-35576 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-35576 is a high-severity cross-site scripting vulnerability in Churchcrm Churchcrm, published on 7 Apr 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-2026-35576 and fix it if it is affected.\n\nWhat it is: CVE-2026-35576 is a high-severity cross-site scripting vulnerability in Churchcrm Churchcrm, published on 7 Apr 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.\nExploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35576 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-35576/ (Markdown: https://insights.sbomify.com/CVE-2026-35576/index.md)","id":"CVE-2026-35576","markdown":"https://insights.sbomify.com/CVE-2026-35576/index.md","name":"CVE-2026-35576","record":{"aliases":["GHSA-8r36-fvxj-26qv"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["account_takeover","data_read"],"network_reachable":"yes","non_default_config":false,"product_category":"ChurchCRM","requires_auth":"low_privilege","summary":"Authenticated users can inject persistent JavaScript via person properties, leading to session hijacking or account compromise for other users.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[{"product":"churchcrm","vendor":"churchcrm"}],"cvss":{"score":8.7,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:H/I:H/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"ChurchCRM is an open-source church management system. Prior to 7.0.0, a stored cross-site scripting (XSS) vulnerability exists in ChurchCRM within the Person Property Management subsystem. This issue persists in versions patched for CVE-2023-38766 and allows an authenticated user to inject arbitrary JavaScript code via dynamically assigned person properties. The malicious payload is persistently stored and executed when other users view the affected person profile or access the printable view, potentially leading to session hijacking or full account compromise. This vulnerability is fixed in 7.0.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 has Stored Cross-Site Scripting (XSS) in Person Properties via PrintView.php","id":"CVE-2026-35576","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":"churchcrm:churchcrm","products":["churchcrm:churchcrm"],"type":"xss","year":"2026"},"n_packages":0,"n_references":2,"next":{"headline":"Missing Host Header Validation in Apollo MCP Server for Localhost Deployments","id":"CVE-2026-35577"},"packages":[],"prev":{"headline":"ChurchCRM has Stored XSS in Group Name","id":"CVE-2026-35575"},"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)"}],"ssvc":{"automatable":"no","exploitation":"poc","technical_impact":"total"},"state":"PUBLISHED","updated":"2026-04-09","vendors":["ChurchCRM"]},"summary":"Authenticated users can inject persistent JavaScript via person properties, leading to session hijacking or account compromise for other users.","url":"https://insights.sbomify.com/CVE-2026-35576/"}