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-67925: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in zozothemes Corpkit

0
High
VulnerabilityCVE-2025-67925cvecve-2025-67925
Published: Thu Jan 08 2026 (01/08/2026, 09:17:47 UTC)
Source: CVE Database V5
Vendor/Project: zozothemes
Product: Corpkit

Description

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in zozothemes Corpkit corpkit allows PHP Local File Inclusion.This issue affects Corpkit: from n/a through <= 2.0.

AI-Powered Analysis

AILast updated: 01/08/2026, 09:55:11 UTC

Technical Analysis

CVE-2025-67925 is a Remote File Inclusion (RFI) vulnerability identified in the PHP theme product Corpkit by zozothemes, affecting versions up to 2.0. The vulnerability stems from improper validation and control of filenames used in PHP include or require statements, which allows an attacker to supply a crafted filename parameter that references a remote malicious PHP file. When the vulnerable application includes this remote file, the attacker's code executes in the context of the web server, leading to remote code execution (RCE). This can allow attackers to execute arbitrary commands, escalate privileges, steal sensitive data, or pivot within the network. The vulnerability is particularly dangerous because it does not require authentication or user interaction, making exploitation straightforward once the vulnerable endpoint is identified. Although no public exploits or patches are currently available, the flaw is classified as a critical security issue due to its impact and ease of exploitation. The vulnerability affects Corpkit versions up to 2.0, a PHP theme product commonly used in content management systems and e-commerce websites. The lack of a CVSS score necessitates a severity assessment based on impact and exploitability factors. The vulnerability compromises confidentiality, integrity, and availability of affected systems, with a broad scope given the widespread use of PHP web applications. The vulnerability was published on January 8, 2026, with the initial reservation date in December 2025. No known exploits in the wild have been reported yet, but the risk remains high given the nature of RFI vulnerabilities.

Potential Impact

The impact of CVE-2025-67925 on European organizations can be severe, especially for those relying on PHP-based web applications using the Corpkit theme. Successful exploitation can lead to full remote code execution, allowing attackers to take control of web servers, access sensitive customer and business data, modify website content, or use the compromised server as a pivot point for further attacks within the corporate network. This can result in data breaches, service disruptions, reputational damage, and regulatory penalties under GDPR. Public-facing websites and e-commerce platforms are particularly at risk, as attackers can exploit the vulnerability to inject malicious payloads, deface websites, or deploy ransomware. The absence of authentication requirements lowers the barrier to exploitation, increasing the likelihood of attacks. Additionally, the vulnerability could be leveraged to distribute malware to European users or to conduct espionage against strategic sectors. Organizations in sectors such as finance, healthcare, government, and critical infrastructure that use Corpkit or derivative PHP themes face heightened risks. The potential for widespread impact is amplified by the common use of PHP in European web hosting environments.

Mitigation Recommendations

To mitigate CVE-2025-67925, organizations should immediately audit their web applications to identify any use of the Corpkit theme up to version 2.0. Since no official patches are currently available, temporary mitigations include disabling or restricting the vulnerable include/require functionality by implementing strict input validation and sanitization on all parameters controlling file inclusion. Employ whitelisting of allowed file paths and disallow remote file inclusion by disabling allow_url_include and allow_url_fopen directives in the PHP configuration. Web application firewalls (WAFs) should be configured to detect and block suspicious file inclusion patterns and remote URL requests. Monitoring web server logs for unusual requests referencing external URLs or unexpected file paths can help detect exploitation attempts. Organizations should also isolate vulnerable systems from critical networks until a patch is released. Once vendor patches or updates become available, they must be applied promptly. Additionally, conducting regular security assessments and penetration testing focused on file inclusion vulnerabilities will help identify and remediate similar issues proactively.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-12-15T09:59:49.436Z
Cvss Version
null
State
PUBLISHED

Threat ID: 695f7a5ac901b06321d0bbee

Added to database: 1/8/2026, 9:35:22 AM

Last enriched: 1/8/2026, 9:55:11 AM

Last updated: 1/9/2026, 7:32:09 AM

Views: 12

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 more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats