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

0
High
VulnerabilityCVE-2025-60060cvecve-2025-60060
Published: Thu Dec 18 2025 (12/18/2025, 07:22:03 UTC)
Source: CVE Database V5
Vendor/Project: axiomthemes
Product: Pubzinne

Description

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

AI-Powered Analysis

AILast updated: 12/18/2025, 08:44:22 UTC

Technical Analysis

CVE-2025-60060 is a vulnerability classified as Improper Control of Filename for Include/Require Statement in PHP programs, specifically affecting the axiomthemes Pubzinne theme up to version 1.0.12. This vulnerability allows for Remote File Inclusion (RFI) or Local File Inclusion (LFI), where an attacker can manipulate the filename parameter used in PHP's include or require statements to load arbitrary files. This can lead to execution of malicious code, disclosure of sensitive files, or full compromise of the web server hosting the vulnerable theme. The root cause is insufficient validation or sanitization of user-controlled input that determines which files are included. Although no CVSS score is assigned yet and no exploits are reported in the wild, the nature of RFI vulnerabilities typically allows unauthenticated attackers to execute arbitrary PHP code remotely, making it a critical risk. The vulnerability affects all versions of Pubzinne up to 1.0.12, and since Pubzinne is a WordPress theme developed by axiomthemes, any WordPress site using this theme is potentially vulnerable. The vulnerability was reserved in September 2025 and published in December 2025, indicating recent discovery. The lack of available patches at the time of reporting means organizations must rely on temporary mitigations such as disabling remote file inclusion in PHP configurations, restricting file inclusion paths, or applying input validation. Given the widespread use of PHP and WordPress in Europe, this vulnerability poses a significant threat to websites using this theme, especially those exposed to the internet without additional protections.

Potential Impact

The impact of CVE-2025-60060 on European organizations can be severe. Successful exploitation allows attackers to execute arbitrary code on the web server, potentially leading to full system compromise, data theft, defacement, or use of the server as a pivot point for further attacks. Confidentiality is at risk due to possible disclosure of sensitive files. Integrity can be compromised by injecting malicious scripts or altering website content. Availability may be affected if attackers disrupt services or deploy ransomware. Organizations relying on axiomthemes Pubzinne for their public-facing websites, especially in sectors like e-commerce, government, or media, face reputational damage and regulatory penalties under GDPR if personal data is exposed. The ease of exploitation without authentication increases the threat level. Since no known exploits are currently in the wild, proactive mitigation is critical to prevent future attacks. The vulnerability also poses risks to hosting providers and managed service providers supporting affected clients in Europe.

Mitigation Recommendations

1. Immediately audit all WordPress installations for the use of the axiomthemes Pubzinne theme and identify versions <= 1.0.12. 2. Apply vendor patches as soon as they are released; monitor axiomthemes and WordPress security advisories closely. 3. In the absence of patches, disable PHP's allow_url_include directive to prevent remote file inclusion. 4. Implement strict input validation and sanitization on any parameters that influence file inclusion paths, using whitelisting approaches. 5. Restrict PHP include paths to trusted directories only, using open_basedir settings. 6. Employ Web Application Firewalls (WAFs) with rules to detect and block suspicious file inclusion attempts. 7. Regularly update PHP and WordPress core to benefit from security improvements. 8. Conduct security awareness training for developers and administrators on secure coding practices related to file inclusion. 9. Monitor logs for unusual access patterns or errors related to file inclusion. 10. Consider isolating vulnerable applications in segmented network zones to limit lateral movement if compromised.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-09-25T15:19:39.457Z
Cvss Version
null
State
PUBLISHED

Threat ID: 6943b04b4eb3efac366ffb11

Added to database: 12/18/2025, 7:42:03 AM

Last enriched: 12/18/2025, 8:44:22 AM

Last updated: 12/19/2025, 5:56:24 AM

Views: 2

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