{"answers":{"affected":"","exploited":"It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58411 exists.","fix":"No fix has been published for CVE-2026-58411 yet. Limit exposure of the affected software until one is available.","what":"CVE-2026-58411 is a high-severity cross-site scripting vulnerability in ChurchCRM CRM, published on 13 Jul 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-2026-58411 and fix it if it is affected.\n\nWhat it is: CVE-2026-58411 is a high-severity cross-site scripting vulnerability in ChurchCRM CRM, published on 13 Jul 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-58411 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-58411/ (Markdown: https://insights.sbomify.com/CVE-2026-58411/index.md)","id":"CVE-2026-58411","markdown":"https://insights.sbomify.com/CVE-2026-58411/index.md","name":"CVE-2026-58411","record":{"aliases":["GHSA-p6j6-vrpg-4pp8"],"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":"none","summary":"Attackers can execute arbitrary scripts in victim browsers via unsanitized request parameters, leading to session theft and account takeover in ChurchCRM.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"GitHub_M","cpe":[],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:L/VA:N/SC:L/SI:L/SA:N","version":"4.0"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"description":"ChurchCRM is an open-source church management system. Prior to version 7.4.0, Cross-Site Scripting (XSS) vulnerabilities were identified due to insufficient output encoding of user-controlled request parameter names and parameter values. The application reflects attacker-controlled input into JavaScript string contexts and HTML attribute contexts without proper sanitization or contextual output encoding. Affected endpoints observed during testing: /FamilyCustomFieldsEditor.php, /PaddleNumList.php and /admin/system/church-info. Potential consequences include session-token theft, account takeover, unauthorized actions on behalf of authenticated users, exposure of sensitive church member information, credential harvesting, phishing, and privilege escalation when administrators are targeted. This issue has been resolved in version 7.4.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 Reflected Cross-Site Scripting (XSS) via unsanitized request parameter names and values","id":"CVE-2026-58411","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2026"},"n_packages":0,"n_references":1,"next":{"headline":"EnvironmentManager.restore() backup ID path traversal copies arbitrary directories into environment data","id":"CVE-2026-58413"},"packages":[],"prev":{"headline":"ChurchCRM: Improper object-level authorization allows low-privileged users to read and modify other families’ records","id":"CVE-2026-58410"},"products":["CRM"],"published":"2026-07-13","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":"partial"},"state":"PUBLISHED","updated":"2026-07-21","vendors":["ChurchCRM"]},"summary":"Attackers can execute arbitrary scripts in victim browsers via unsanitized request parameters, leading to session theft and account takeover in ChurchCRM.","url":"https://insights.sbomify.com/CVE-2026-58411/"}