Súbít #669916: ChurchCRM ChurchCRM (GitHub: ChurchCRM/CRM) <= 5.18.0 Authentication Bypass / Access Controlbayani

KuraChurchCRM ChurchCRM (GitHub: ChurchCRM/CRM) <= 5.18.0 Authentication Bypass / Access Control
GaskiyaA critical authentication bypass in ChurchCRM’s API middleware allows unauthenticated attackers to access protected API endpoints by including the substring api/public anywhere in the request URI (path, query string, or fragment). The middleware used str_contains($request->getUri(), 'api/public'), which matched the full URI instead of only the path. An attacker can bypass authentication by adding a query parameter such as ?bypass=api/public, resulting in exposure and potential modification of sensitive data (member records, family relationships), triggering background jobs, abusing geocoding endpoints, and deleting calendar entries where allowed.
Manga⚠️ https://github.com/uartu0/advisories/blob/main/churchcrm-api-auth-bypass-2025.md
Màdùmga
 uartu0 (UID 90021)
Furta10/06/2025 16:17 (4 Wurɗi 전)
Gargajiya10/08/2025 21:14 (2 days later)
HalittaShingilam
VulDB gite327667 [ChurchCRM har 5.18.0 API Endpoint AuthMiddleware.php AuthMiddleware karkar ndiyamga taƙa]
Nganji20

Do you want to use VulDB in your project?

Use the official API to access entries easily!