Skip to content

RCE with database restore funcionality

Critical
DawoudIO published GHSA-pqm7-g8px-9r77 Dec 17, 2025

Package

No package listed

Affected versions

6.2.0

Patched versions

6.5.3

Description

Summary

It was identified that the Database Restore functionality does not validate the content or file extension of uploaded files. As a result, an attacker can upload a web shell file and subsequently upload a .htaccess file to enable direct access to it. Once accessed, the uploaded web shell allows remote code execution (RCE) on the server.

Details

First, the attacker uploads a web shell file to the system.

image image

then we add .htaccess file to make the directory accessible

image

then we can acces and have a web shell on the server as seen below;

image

Impact

Exploitation of this vulnerability results in full Remote Code Execution (RCE) on the underlying server. By abusing the insecure file upload logic in the Database Restore functionality, an attacker can upload a web shell and subsequently activate it by manipulating .htaccess rules. Once executed, the web shell provides direct command execution capabilities on the operating system with the privileges of the web server user.

This level of access completely compromises the confidentiality, integrity, and availability of the system. The attacker can read, modify, or delete any application files, including configuration files containing database credentials. Access to these credentials enables full control over the application database, allowing unauthorized manipulation of user data, financial records, internal configurations, and audit logs.

Furthermore, obtaining OS-level command execution allows the attacker to pivot laterally within the server environment, escalate privileges through local misconfigurations, implant backdoors, exfiltrate sensitive data, or abuse the server as part of a broader attack chain (e.g., staging malware, hosting phishing pages, or launching attacks against internal systems).

Because the attack breaks isolation between the application layer and the operating system, the impact extends far beyond the scope of the ChurchCRM application itself. This qualifies as a complete system compromise and should be treated as a critical security risk requiring immediate remediation.

Severity

Critical

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
Low
Privileges required
High
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H

CVE ID

CVE-2025-68109

Weaknesses

Improper Neutralization of Special Elements used in an OS Command ('OS Command Injection')

The product constructs all or part of an OS command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended OS command when it is sent to a downstream component. Learn more on MITRE.

Unrestricted Upload of File with Dangerous Type

The product allows the upload or transfer of dangerous file types that are automatically processed within its environment. Learn more on MITRE.

Download of Code Without Integrity Check

The product downloads source code or an executable from a remote location and executes the code without sufficiently verifying the origin and integrity of the code. Learn more on MITRE.

Files or Directories Accessible to External Parties

The product makes files or directories accessible to unauthorized actors, even though they should not be. Learn more on MITRE.

Improperly Controlled Modification of Dynamically-Determined Object Attributes

The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified. Learn more on MITRE.

Credits