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-68987: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') in Edge-Themes Cinerama - A WordPress Theme for Movie Studios and Filmmakers

0
Critical
VulnerabilityCVE-2025-68987cvecve-2025-68987
Published: Tue Dec 30 2025 (12/30/2025, 10:47:49 UTC)
Source: CVE Database V5
Vendor/Project: Edge-Themes
Product: Cinerama - A WordPress Theme for Movie Studios and Filmmakers

Description

Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in Edge-Themes Cinerama - A WordPress Theme for Movie Studios and Filmmakers cinerama allows PHP Local File Inclusion.This issue affects Cinerama - A WordPress Theme for Movie Studios and Filmmakers: from n/a through <= 2.4.

AI-Powered Analysis

AILast updated: 01/21/2026, 01:48:48 UTC

Technical Analysis

CVE-2025-68987 is a critical vulnerability classified as a Remote File Inclusion (RFI) flaw in the Edge-Themes Cinerama WordPress theme, which is tailored for movie studios and filmmakers. The vulnerability arises from improper control over the filename parameter used in PHP's include or require statements, allowing an attacker to specify arbitrary files to be included and executed by the server. This flaw affects all versions of the Cinerama theme up to and including version 2.4. Because PHP include/require statements execute code from the specified files, an attacker can remotely include malicious PHP scripts hosted on external servers, leading to remote code execution (RCE). The vulnerability requires no authentication and no user interaction, making it trivially exploitable over the network. The CVSS 3.1 base score of 9.8 reflects the critical nature of this vulnerability, with attack vector being network-based, low attack complexity, no privileges required, no user interaction, and high impact on confidentiality, integrity, and availability. The vulnerability can lead to full system compromise, data exfiltration, defacement, or pivoting within the victim's network. Although no known exploits have been reported in the wild yet, the widespread use of WordPress and the popularity of the Cinerama theme in the media sector make this a high-risk issue. The lack of official patches or updates at the time of disclosure increases the urgency for mitigation.

Potential Impact

For European organizations, especially those in the media, entertainment, and creative industries that rely on WordPress and specifically the Cinerama theme, this vulnerability poses a severe risk. Successful exploitation can lead to complete compromise of web servers, exposing sensitive intellectual property, client data, and internal communications. The integrity of websites can be undermined, leading to reputational damage and loss of customer trust. Availability may also be impacted if attackers deploy ransomware or defacement attacks. Given the criticality and ease of exploitation, attackers could leverage this vulnerability to establish persistent footholds, move laterally within networks, or launch further attacks against European infrastructure. Regulatory implications under GDPR may also arise due to potential data breaches. The threat is particularly acute for organizations that have not implemented timely patching or lack robust web application security controls.

Mitigation Recommendations

Immediate mitigation steps include: 1) Updating the Cinerama theme to a patched version once available from Edge-Themes. If no patch exists yet, consider temporarily disabling or removing the theme to prevent exploitation. 2) Implement strict input validation and sanitization on all parameters that control file inclusion to prevent injection of arbitrary file paths or URLs. 3) Deploy a Web Application Firewall (WAF) with rules to detect and block suspicious include/require parameter usage and known attack patterns related to RFI. 4) Restrict PHP configuration settings such as disabling allow_url_include and enabling open_basedir restrictions to limit file inclusion to trusted directories. 5) Conduct thorough security audits and monitoring of web server logs for unusual requests or file access patterns. 6) Educate site administrators on the risks and ensure timely application of security updates. 7) Employ network segmentation to limit the impact of a compromised web server on internal systems. These measures, combined, reduce the attack surface and improve detection and response capabilities.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-12-29T11:18:04.294Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 695450a0db813ff03e2bda4c

Added to database: 12/30/2025, 10:22:24 PM

Last enriched: 1/21/2026, 1:48:48 AM

Last updated: 2/7/2026, 5:15:07 PM

Views: 33

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