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

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

Description

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

AI-Powered Analysis

AILast updated: 01/20/2026, 21:14:16 UTC

Technical Analysis

CVE-2025-58950 is a Remote File Inclusion (RFI) vulnerability found in the axiomthemes Lione WordPress theme, specifically in versions up to and including 1.16. The vulnerability arises due to improper control and validation of filenames used in PHP include or require statements. This flaw allows an attacker to manipulate the filename parameter to include remote PHP files hosted on attacker-controlled servers. When the vulnerable code executes the include or require statement with the malicious filename, it results in the execution of arbitrary PHP code on the target server. This can lead to a full compromise of the web server, including data theft, website defacement, or pivoting to internal networks. The CVSS v3.1 score of 8.1 indicates a high-severity issue, with an attack vector of network (AV:N), low attack complexity (AC:L), no privileges required (PR:N), but requiring user interaction (UI:R). The scope is unchanged (S:U), and the impact on confidentiality and integrity is high (C:H/I:H), while availability impact is none (A:N). The vulnerability was reserved in September 2025 and published in December 2025. No public exploits are known yet, but the nature of RFI vulnerabilities historically makes them attractive targets. The affected product, Lione, is a WordPress theme by axiomthemes, commonly used for business and portfolio websites. The lack of patch links suggests a patch may not yet be available, emphasizing the need for immediate mitigation steps.

Potential Impact

For European organizations, this vulnerability poses significant risks, especially for those relying on the Lione theme for their public-facing websites. Successful exploitation can lead to unauthorized disclosure of sensitive data, including customer information and internal business data, violating GDPR and other data protection regulations. The integrity of websites can be compromised, leading to defacement or the injection of malicious content such as malware or phishing pages, damaging brand reputation and customer trust. Although availability impact is not directly indicated, indirect effects such as website downtime due to cleanup or mitigation efforts can occur. Organizations in sectors like finance, healthcare, and e-commerce, which often use WordPress themes for their web presence, are particularly vulnerable. The ease of exploitation without authentication and the requirement for only user interaction (e.g., visiting a malicious URL) increase the likelihood of successful attacks. Additionally, compromised websites can be used as launchpads for further attacks within European networks or to distribute malware to European users.

Mitigation Recommendations

1. Immediately monitor for updates or patches released by axiomthemes for the Lione theme and apply them as soon as available. 2. Until a patch is available, implement manual code review and hardening: sanitize and validate all inputs that control include or require statements to ensure only allowed local files can be included. 3. Employ Web Application Firewalls (WAFs) with custom rules to detect and block suspicious requests attempting to exploit file inclusion vulnerabilities. 4. Restrict PHP configuration settings such as disabling allow_url_include and allow_url_fopen to prevent remote file inclusion. 5. Conduct regular security audits and vulnerability scans focused on WordPress themes and plugins to detect similar issues proactively. 6. Educate website administrators and users about the risks of clicking on untrusted links that could trigger exploitation. 7. Implement strict access controls and monitoring on web servers hosting WordPress sites to detect anomalous behavior quickly. 8. Consider isolating WordPress installations in containerized or sandboxed environments to limit the blast radius of potential compromises.

Need more detailed analysis?Upgrade to Pro Console

Technical Details

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

Threat ID: 6943b0474eb3efac366ff9a0

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

Last enriched: 1/20/2026, 9:14:16 PM

Last updated: 2/7/2026, 9:36:55 PM

Views: 39

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