# CVE-2026-40480: ChurchCRM has Missing Object-Level Authorization / IDOR in `/api/person/{personId}`

> Authenticated users can read other members' personal information via the API due to missing object-level authorization checks.

- **Severity:** High 7.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Apr 2026
- **Updated:** 20 Apr 2026
- **Also known as:** GHSA-5w59-32c8-933v

## What is CVE-2026-40480?

CVE-2026-40480 is a high-severity missing authorization vulnerability in ChurchCRM CRM, published on 17 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ChurchCRM is an open-source church management system. In versions prior to 7.2.0, the GET /api/person/{personId} endpoint loads and returns person records without performing object-level authorization checks. Although the legacy PersonView.php page enforces canEditPerson() restrictions, the API layer omits this check. Any authenticated user with only EditSelf privileges can enumerate and read other members' records, exposing sensitive PII including names, addresses, phone numbers, and email addresses. This issue has been fixed in version 7.2.0.

Weakness: CWE-862 (Missing Authorization), CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2026-40480 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40480 is a high-severity missing authorization vulnerability in ChurchCRM CRM, published on 17 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-40480 exists.

Affected product: ChurchCRM CRM. 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-40480/ (Markdown: https://insights.sbomify.com/CVE-2026-40480/index.md)
```

## Sources

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

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