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

0
Critical
VulnerabilityCVE-2025-68530cvecve-2025-68530
Published: Wed Dec 24 2025 (12/24/2025, 12:31:26 UTC)
Source: CVE Database V5
Vendor/Project: pavothemes
Product: Bookory

Description

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

AI-Powered Analysis

AILast updated: 01/21/2026, 01:28:57 UTC

Technical Analysis

CVE-2025-68530 is a critical vulnerability classified as Remote File Inclusion (RFI) in the pavothemes Bookory WordPress theme, affecting versions up to and including 2.2.7. The flaw arises from improper control of the filename parameter used in PHP include or require statements, allowing an attacker to specify a remote file to be included and executed by the server. This vulnerability does not require authentication or user interaction, making it remotely exploitable over the network. Successful exploitation leads to arbitrary code execution with the privileges of the web server process, potentially allowing attackers to execute malicious scripts, escalate privileges, access sensitive data, or disrupt website availability. The CVSS v3.1 score of 9.8 reflects its critical nature, with network attack vector, low attack complexity, no privileges required, and no user interaction needed. Although no public exploits are currently known, the vulnerability's characteristics make it a prime target for attackers. The Bookory theme is used primarily in WordPress environments, which are widely deployed across various industries. The lack of available patches at the time of disclosure increases the urgency for mitigation. This vulnerability highlights the risks of insecure coding practices in PHP applications, especially in popular CMS themes that can serve as a widespread attack surface.

Potential Impact

For European organizations, this vulnerability poses a severe risk to websites running the Bookory theme on WordPress. Exploitation can lead to full compromise of the affected web server, resulting in data breaches, defacement, malware distribution, or use of the server as a pivot point for further network attacks. Organizations in sectors such as e-commerce, media, education, and government that rely on WordPress for public-facing sites are particularly vulnerable. The compromise of these sites can damage reputation, lead to regulatory penalties under GDPR due to data exposure, and cause operational disruptions. Since the vulnerability allows remote code execution without authentication, attackers can rapidly exploit unpatched systems at scale. The widespread use of WordPress in Europe, combined with the critical severity of this flaw, means that many organizations could be impacted if timely remediation is not applied. Additionally, the potential for automated exploitation tools to emerge increases the risk of mass exploitation campaigns targeting European infrastructure.

Mitigation Recommendations

Immediate mitigation steps include: 1) Applying any available patches or updates from pavothemes as soon as they are released. 2) If patches are not yet available, temporarily disabling or removing the Bookory theme from production environments to eliminate the attack vector. 3) Implementing web application firewalls (WAFs) with rules to detect and block attempts to exploit file inclusion vulnerabilities, such as requests containing suspicious URL parameters or remote file paths. 4) Restricting PHP configuration settings to disable remote file inclusion (e.g., setting 'allow_url_include' to 'Off' and 'allow_url_fopen' to 'Off' where feasible). 5) Reviewing and tightening file and directory permissions on web servers to limit the impact of potential code execution. 6) Monitoring web server logs and network traffic for unusual activity indicative of exploitation attempts. 7) Educating development and operations teams about secure coding practices to prevent similar vulnerabilities. 8) Considering isolating WordPress instances in segmented network zones to reduce lateral movement risk. These measures, combined with prompt patching, will significantly reduce the risk posed by this vulnerability.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-12-19T10:17:03.706Z
Cvss Version
null
State
PUBLISHED

Threat ID: 694bdf88279c98bf57ee5773

Added to database: 12/24/2025, 12:41:44 PM

Last enriched: 1/21/2026, 1:28:57 AM

Last updated: 2/7/2026, 10:45:17 AM

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