Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-52768: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in AncoraThemes Faith & Hope

0
High
VulnerabilityCVE-2025-52768cvecve-2025-52768
Published: Thu Dec 18 2025 (12/18/2025, 07:21:45 UTC)
Source: CVE Database V5
Vendor/Project: AncoraThemes
Product: Faith & Hope

Description

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in AncoraThemes Faith & Hope faith-hope allows PHP Local File Inclusion.This issue affects Faith & Hope: from n/a through <= 2.13.0.

AI-Powered Analysis

AILast updated: 12/18/2025, 09:45:08 UTC

Technical Analysis

CVE-2025-52768 is a vulnerability classified as Improper Control of Filename for Include/Require Statement in PHP programs, specifically affecting the AncoraThemes Faith & Hope WordPress theme versions up to 2.13.0. This vulnerability allows Remote File Inclusion (RFI), where an attacker can manipulate the filename parameter used in PHP include or require statements to load arbitrary files from remote or local sources. This occurs due to insufficient validation or sanitization of user-supplied input controlling the file path. Successful exploitation can lead to arbitrary code execution on the server, enabling attackers to run malicious PHP code, steal sensitive data, modify website content, or pivot further into the hosting environment. Although the vulnerability is labeled as PHP Local File Inclusion in the description, the nature of improper filename control typically enables remote inclusion if PHP's allow_url_include directive is enabled, which is common in some hosting environments. The vulnerability affects the AncoraThemes Faith & Hope theme, a WordPress theme used for websites, potentially exposing numerous WordPress installations. No CVSS score has been assigned yet, and no public exploits are known at this time. The vulnerability was reserved in June 2025 and published in December 2025, indicating recent discovery. The lack of patch links suggests a patch may not yet be publicly available, increasing urgency for mitigations. The vulnerability's impact is severe due to the possibility of full site compromise without requiring authentication or user interaction, making it a critical risk for affected sites.

Potential Impact

For European organizations, the impact of CVE-2025-52768 can be substantial, especially for those relying on WordPress websites using the AncoraThemes Faith & Hope theme. Exploitation can lead to unauthorized remote code execution, allowing attackers to deface websites, steal sensitive customer or business data, deploy malware, or use compromised servers as launchpads for further attacks. This can result in reputational damage, regulatory non-compliance (e.g., GDPR violations due to data breaches), financial losses, and operational disruptions. Public-facing websites of e-commerce, governmental, educational, or healthcare organizations are particularly at risk. Additionally, compromised web servers can be leveraged to attack internal networks, increasing the scope of impact. The absence of a patch at the time of publication means organizations must rely on interim mitigations, increasing exposure duration. The vulnerability's ease of exploitation without authentication or user interaction further elevates the risk profile for European entities hosting vulnerable themes.

Mitigation Recommendations

1. Immediate identification of all WordPress installations using the AncoraThemes Faith & Hope theme, especially versions up to 2.13.0, via inventory and scanning tools. 2. Monitor AncoraThemes official channels and Patchstack for release of security patches and apply updates promptly once available. 3. Until patches are released, disable PHP's allow_url_include directive in php.ini to prevent remote file inclusion. 4. Implement web application firewall (WAF) rules to detect and block suspicious requests attempting to exploit file inclusion vectors, focusing on parameters controlling file paths. 5. Harden input validation by restricting or sanitizing inputs that influence include/require statements, possibly via custom code or security plugins. 6. Restrict file permissions on web servers to limit PHP's ability to include arbitrary files outside intended directories. 7. Conduct regular security audits and penetration tests focusing on file inclusion vulnerabilities. 8. Educate web administrators and developers about secure coding practices related to file inclusion. 9. Consider isolating vulnerable web applications in segmented network zones to limit lateral movement if compromised. 10. Maintain comprehensive backups to enable rapid recovery in case of compromise.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-06-19T10:03:09.015Z
Cvss Version
null
State
PUBLISHED

Threat ID: 6943b0394eb3efac366ff214

Added to database: 12/18/2025, 7:41:45 AM

Last enriched: 12/18/2025, 9:45:08 AM

Last updated: 12/19/2025, 7:25:53 AM

Views: 4

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats