# CVE-2026-35572: SSRF via Referer header in ChurchCRM allows server-side HTTP/HTTPS requests to arbitrary hosts

> Attackers can force the ChurchCRM server to make arbitrary HTTP/HTTPS requests via the Referer header, potentially accessing internal resources.

- **Severity:** High 7.0 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 7 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-44x3-28jv-mrwq

## What is CVE-2026-35572?

CVE-2026-35572 is a high-severity server-side request forgery vulnerability in Churchcrm Churchcrm, published on 7 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

ChurchCRM is an open-source church management system. Prior to 6.5.3, it is possible to trigger server-side HTTP/HTTPS requests to arbitrary hosts (SSRF) by supplying a crafted URL in the Referer request header. The server subsequently makes an outbound request to the attacker-controlled domain, confirmed via OAST. This vulnerability is fixed in 6.5.3.

Weakness: CWE-918 (Server-Side Request Forgery)

## Which versions are affected by CVE-2026-35572?

It affects 1 product.


Products: Churchcrm Churchcrm.

## How do I fix CVE-2026-35572?

No fix has been published for CVE-2026-35572 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-35572 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35572 exists.

## Other vulnerabilities in Churchcrm Churchcrm

- [CVE-2026-39337](https://insights.sbomify.com/CVE-2026-39337/): ChurchCRM Affected by Unauthenticated RCE in Install Wizard (critical 10.0)
- [CVE-2025-62521](https://insights.sbomify.com/CVE-2025-62521/): ChurchCRM has unauthenticated RCE in its Install Wizard (critical 10.0)
- [CVE-2025-68110](https://insights.sbomify.com/CVE-2025-68110/): ChurchCRM discloses database information on error message (critical 10.0)
- [CVE-2024-53438](https://insights.sbomify.com/CVE-2024-53438/): SQL injection in n/a (critical 9.8)
- [CVE-2024-25894](https://insights.sbomify.com/CVE-2024-25894/): SQL injection in n/a (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-35572 and fix it if it is affected.

What it is: CVE-2026-35572 is a high-severity server-side request forgery vulnerability in Churchcrm Churchcrm, published on 7 Apr 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-35572 exists.

Affected product: Churchcrm Churchcrm. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-35572/ (Markdown: https://insights.sbomify.com/CVE-2026-35572/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-35572
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-35572
- OSV: https://osv.dev/vulnerability/CVE-2026-35572

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-35572/
Summaries are generated and may contain mistakes; the official description above is the record.