CVE-2025-27015

Hostiko - Hosting WordPress & WHMCS Theme < 30.1 - Unauthenticated Local File Inclusion

2025-02-18 00:00
Bonds

Strategic Overview

Status
Patched in 30.1
Affected Version
< 30.1
CVSS
8.1High
Weakness type
CWE-98 · Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')
CVE
CVE-2025-27015
View all Hostiko - Hosting WordPress & WHMCS Theme vulnerabilities

At a glance

CVE-2025-27015 is a high-severity Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in the Hostiko - Hosting WordPress & WHMCS Theme WordPress theme, affecting versions < 30.1. It carries a CVSS score of 8.1 (reachable over the network; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 30.1; sites on affected versions should update now. Disclosed February 2025, reported by Bonds.

Vulnerability Overview

The Hostiko - Hosting WordPress & WHMCS Theme theme for WordPress is vulnerable to Local File Inclusion in all versions up to 30.1 (exclusive). This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion')

Hostiko - Hosting WordPress & WHMCS Theme < 30.1 carries this weakness at safe, and reaching it takes no account at all. PHP file inclusion means a path used by include or require is built from request data, so the file that gets executed is under the caller's influence.

Including an attacker-influenced file executes its contents, which is why this class is routinely chained with an upload or log-poisoning step to reach code execution. For Hostiko - Hosting WordPress & WHMCS Theme the fix is 30.1: builds < 30.1 are affected, anything from 30.1 onward is not.

Remediation

Update to version 30.1, or a newer patched version

How does WordSec protect against this?

Requests carrying this pattern arrive without a session, so nothing upstream of the firewall gets a chance to reject them: WordSec's web application firewall inspects request payloads before WordPress loads them. Classes like this one can leave something behind, so the staged malware scanner is the second half: it looks for dropped files and modified code rather than for the request that created them. None of that substitutes for the fix: Hostiko - Hosting WordPress & WHMCS Theme 30.1 closes this, and updating the theme is the step that ends it.

  • Firewall
  • Scanner
  • Login Security

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C