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

0
High
VulnerabilityCVE-2025-58937cvecve-2025-58937
Published: Thu Dec 18 2025 (12/18/2025, 07:21:57 UTC)
Source: CVE Database V5
Vendor/Project: axiomthemes
Product: Tacticool

Description

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

AI-Powered Analysis

AILast updated: 01/20/2026, 21:10:30 UTC

Technical Analysis

CVE-2025-58937 is a Remote File Inclusion (RFI) vulnerability found in the axiomthemes Tacticool WordPress theme, affecting versions up to 1.0.13. The vulnerability arises from improper validation and control of filenames used in PHP include or require statements, allowing an attacker to specify a remote file URL that the server will include and execute. This can lead to arbitrary code execution on the server, compromising confidentiality and integrity of the system. The vulnerability is remotely exploitable over the network without authentication, though it requires user interaction such as visiting a maliciously crafted URL. The CVSS 3.1 score of 8.1 indicates a high severity, with attack vector being network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), user interaction required (UI:R), unchanged scope (S:U), and high impact on confidentiality and integrity (C:H/I:H) but no impact on availability (A:N). The vulnerability affects a widely used WordPress theme, which may be deployed on numerous websites, increasing the potential attack surface. Although no public exploits are currently known, the nature of RFI vulnerabilities and their history suggest a high risk of exploitation once details become widely known. The vulnerability was reserved in September 2025 and published in December 2025, indicating recent discovery and disclosure. Lack of official patches or updates at the time of reporting increases urgency for mitigation.

Potential Impact

For European organizations, this vulnerability poses a significant risk to websites running the Tacticool theme, potentially leading to unauthorized remote code execution, data theft, defacement, or use of compromised servers as pivot points for further attacks. Confidential customer data and internal information could be exposed or manipulated, damaging reputation and violating data protection regulations such as GDPR. The integrity of web applications and backend systems could be compromised, leading to loss of trust and operational disruptions. Given the high CVSS score and the nature of the vulnerability, attackers could leverage this flaw to implant backdoors or malware, facilitating persistent access. The impact is particularly severe for organizations relying on WordPress for customer-facing portals, e-commerce, or internal tools. Without timely mitigation, attackers could exploit this vulnerability to conduct espionage, financial fraud, or disrupt services. The lack of known exploits currently provides a window for proactive defense, but the risk of rapid weaponization is high.

Mitigation Recommendations

European organizations should immediately audit their WordPress installations to identify use of the Tacticool theme, specifically versions up to 1.0.13. If found, they should apply any available patches or updates from axiomthemes as soon as they are released. In the absence of official patches, organizations should implement strict input validation and sanitization on any parameters that influence include or require statements in PHP code. Web application firewalls (WAFs) should be configured to detect and block suspicious requests attempting remote file inclusion, such as those containing URL schemes or suspicious file paths. Disabling allow_url_include and allow_url_fopen directives in PHP configurations can mitigate remote file inclusion risks. Regularly monitoring web server logs for anomalous requests and scanning for webshells or unauthorized files is critical. Organizations should also consider isolating WordPress environments and limiting permissions to reduce potential damage from exploitation. Finally, educating web administrators about the risks and signs of exploitation can improve detection and response.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

Data Version
5.2
Assigner Short Name
Patchstack
Date Reserved
2025-09-06T04:44:48.015Z
Cvss Version
null
State
PUBLISHED

Threat ID: 6943b0454eb3efac366ff8db

Added to database: 12/18/2025, 7:41:57 AM

Last enriched: 1/20/2026, 9:10:30 PM

Last updated: 2/5/2026, 1:56:49 PM

Views: 21

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