CVE-2025-68112
BaseFortify
Publication date: 2025-12-17
Last updated on: 2025-12-18
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| churchcrm | churchcrm | to 6.5.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This SQL injection vulnerability can be detected by testing the Event ID (EID) parameter in POST requests to the EditEventAttendees.php endpoint for improper input sanitization. For example, sending a POST request with the EID parameter set to a typical injection payload such as `' OR 1=1--` can cause an SQL error (HTTP 500), indicating vulnerability. Additionally, a UNION SELECT injection payload can be used to confirm data extraction capability. Commands using curl to test this might look like: 1) Normal request: `curl -X POST -d "EID=1" http://yourchurchcrmserver/EditEventAttendees.php` 2) Injection test: `curl -X POST -d "EID=' OR 1=1--" http://yourchurchcrmserver/EditEventAttendees.php` Observing an HTTP 500 error or unexpected data in the response suggests the presence of the vulnerability. [1]
Can you explain this vulnerability to me?
This vulnerability is a SQL injection flaw in ChurchCRM's Event Attendee Editor that affects versions prior to 6.5.3. It allows authenticated users to execute arbitrary SQL commands on the database, which can lead to complete database compromise, theft of administrative credentials, and potential takeover of the entire system.
How can this vulnerability impact me? :
The vulnerability can lead to attackers extracting sensitive member data, authentication credentials, and financial information from the church management system. It can also result in administrative credential theft and potential full system takeover, severely impacting the confidentiality and integrity of your data and system.
What immediate steps should I take to mitigate this vulnerability?
Upgrade ChurchCRM to version 6.5.3 or later, as this version contains the patch that fixes the SQL injection vulnerability in the Event Attendee Editor.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
This vulnerability allows attackers to extract sensitive member data, authentication credentials, and financial information, which could lead to non-compliance with data protection regulations such as GDPR and HIPAA due to unauthorized data access and potential data breaches.