CVE-2025-68065: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in LiquidThemes Hub Core
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in LiquidThemes Hub Core hub-core allows PHP Local File Inclusion.This issue affects Hub Core: from n/a through <= 5.0.8.
AI Analysis
Technical Summary
CVE-2025-68065 is a vulnerability classified as Improper Control of Filename for Include/Require Statement in PHP programs, specifically affecting the LiquidThemes Hub Core product up to version 5.0.8. This vulnerability enables Remote File Inclusion (RFI) or Local File Inclusion (LFI) attacks by allowing an attacker to manipulate the filename parameter used in PHP's include or require statements without proper validation or sanitization. When exploited, an attacker can force the application to include and execute malicious code from a remote server or local file, leading to arbitrary code execution, data leakage, or complete system compromise. The vulnerability stems from insufficient input validation controls in the Hub Core codebase, which fails to restrict or sanitize user-supplied input that determines the file to be included. Although no public exploits have been reported yet, the nature of RFI/LFI vulnerabilities makes them highly exploitable, especially in web-facing environments. The vulnerability affects all versions up to and including 5.0.8, with no patch currently linked or available, indicating that users must monitor vendor updates closely. The vulnerability was reserved and published in December 2025, highlighting its recent discovery. Due to the widespread use of PHP in web applications and the popularity of LiquidThemes products in content management and e-commerce, this vulnerability poses a significant risk to organizations relying on Hub Core for their web infrastructure.
Potential Impact
The impact of CVE-2025-68065 on European organizations can be severe. Successful exploitation can lead to remote code execution, allowing attackers to take full control of affected web servers. This can result in data breaches involving sensitive customer or business data, defacement of websites, disruption of services, and use of compromised servers as pivot points for further attacks within corporate networks. For organizations in sectors such as finance, healthcare, and e-commerce, the confidentiality, integrity, and availability of critical systems could be compromised, leading to regulatory penalties under GDPR and loss of customer trust. Additionally, the ease of exploitation without authentication increases the attack surface, especially for public-facing web applications. The lack of a current patch means organizations must rely on temporary mitigations, increasing operational risk. European companies using Hub Core in multi-tenant or cloud environments may face cascading effects if attackers leverage this vulnerability to move laterally. Overall, the threat could disrupt business continuity and cause significant financial and reputational damage.
Mitigation Recommendations
To mitigate CVE-2025-68065, organizations should immediately audit their use of LiquidThemes Hub Core and identify affected versions (<=5.0.8). Until an official patch is released, implement strict input validation and sanitization on all parameters that influence file inclusion paths, employing whitelisting of allowed files and directories. Disable remote file inclusion in PHP configurations by setting 'allow_url_include' to 'Off' and 'allow_url_fopen' to 'Off' where feasible. Employ Web Application Firewalls (WAFs) with rules to detect and block suspicious include/require patterns and anomalous HTTP requests. Conduct code reviews to identify and refactor unsafe include/require statements. Restrict file system permissions to limit the impact of potential file inclusion. Monitor logs for unusual file access or inclusion attempts. Prepare incident response plans for potential exploitation scenarios. Finally, stay alert for vendor patches or updates and apply them promptly once available.
Affected Countries
Germany, France, United Kingdom, Italy, Spain, Netherlands, Poland
CVE-2025-68065: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in LiquidThemes Hub Core
Description
Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in LiquidThemes Hub Core hub-core allows PHP Local File Inclusion.This issue affects Hub Core: from n/a through <= 5.0.8.
AI-Powered Analysis
Technical Analysis
CVE-2025-68065 is a vulnerability classified as Improper Control of Filename for Include/Require Statement in PHP programs, specifically affecting the LiquidThemes Hub Core product up to version 5.0.8. This vulnerability enables Remote File Inclusion (RFI) or Local File Inclusion (LFI) attacks by allowing an attacker to manipulate the filename parameter used in PHP's include or require statements without proper validation or sanitization. When exploited, an attacker can force the application to include and execute malicious code from a remote server or local file, leading to arbitrary code execution, data leakage, or complete system compromise. The vulnerability stems from insufficient input validation controls in the Hub Core codebase, which fails to restrict or sanitize user-supplied input that determines the file to be included. Although no public exploits have been reported yet, the nature of RFI/LFI vulnerabilities makes them highly exploitable, especially in web-facing environments. The vulnerability affects all versions up to and including 5.0.8, with no patch currently linked or available, indicating that users must monitor vendor updates closely. The vulnerability was reserved and published in December 2025, highlighting its recent discovery. Due to the widespread use of PHP in web applications and the popularity of LiquidThemes products in content management and e-commerce, this vulnerability poses a significant risk to organizations relying on Hub Core for their web infrastructure.
Potential Impact
The impact of CVE-2025-68065 on European organizations can be severe. Successful exploitation can lead to remote code execution, allowing attackers to take full control of affected web servers. This can result in data breaches involving sensitive customer or business data, defacement of websites, disruption of services, and use of compromised servers as pivot points for further attacks within corporate networks. For organizations in sectors such as finance, healthcare, and e-commerce, the confidentiality, integrity, and availability of critical systems could be compromised, leading to regulatory penalties under GDPR and loss of customer trust. Additionally, the ease of exploitation without authentication increases the attack surface, especially for public-facing web applications. The lack of a current patch means organizations must rely on temporary mitigations, increasing operational risk. European companies using Hub Core in multi-tenant or cloud environments may face cascading effects if attackers leverage this vulnerability to move laterally. Overall, the threat could disrupt business continuity and cause significant financial and reputational damage.
Mitigation Recommendations
To mitigate CVE-2025-68065, organizations should immediately audit their use of LiquidThemes Hub Core and identify affected versions (<=5.0.8). Until an official patch is released, implement strict input validation and sanitization on all parameters that influence file inclusion paths, employing whitelisting of allowed files and directories. Disable remote file inclusion in PHP configurations by setting 'allow_url_include' to 'Off' and 'allow_url_fopen' to 'Off' where feasible. Employ Web Application Firewalls (WAFs) with rules to detect and block suspicious include/require patterns and anomalous HTTP requests. Conduct code reviews to identify and refactor unsafe include/require statements. Restrict file system permissions to limit the impact of potential file inclusion. Monitor logs for unusual file access or inclusion attempts. Prepare incident response plans for potential exploitation scenarios. Finally, stay alert for vendor patches or updates and apply them promptly once available.
Affected Countries
For access to advanced analysis and higher rate limits, contact root@offseq.com
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Patchstack
- Date Reserved
- 2025-12-15T10:01:19.544Z
- Cvss Version
- null
- State
- PUBLISHED
Threat ID: 69411756594e45819d70d835
Added to database: 12/16/2025, 8:24:54 AM
Last enriched: 12/16/2025, 8:50:08 AM
Last updated: 12/16/2025, 10:59:53 AM
Views: 3
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Related Threats
CVE-2025-14002: CWE-287 Improper Authentication in whyun WPCOM Member
HighCVE-2025-13231: CWE-362 Concurrent Execution using Shared Resource with Improper Synchronization ('Race Condition') in radykal Fancy Product Designer
MediumCVE-2025-68088: Missing Authorization in merkulove Huger for Elementor
UnknownCVE-2025-68087: Missing Authorization in merkulove Modalier for Elementor
UnknownCVE-2025-68086: Missing Authorization in merkulove Reformer for Elementor
UnknownActions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
External Links
Need enhanced features?
Contact root@offseq.com for Pro access with improved analysis and higher rate limits.