Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSend crafted request to vulnerable parameter
-
ExploitBypass path/input filtering
-
ExecutionForce PHP to include local file
-
ImpactDisclose sensitive file contents
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V5 - File Handling File inclusion prevention, allowlisting
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Command and Control The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Affects sites running the Biolife WordPress theme at version 3.2.3 or earlier. Exploitation is unauthenticated and remote (PR:N/UI:N), but the vendor's AC:H rating indicates success is not guaranteed on a single attempt and depends on conditions the attacker does not fully control - the description does not name the exact vulnerable parameter, required encoding, or configuration, so the precise trigger is unconfirmed from available data. The primary realistic impact is disclosure of local files (e.g., configuration or credential files); escalation to code execution is possible for CWE-98 but not established here. The main limiting factor is that only Biolife-theme installations at or below 3.2.3 are affected, a niche footprint, and the high complexity reduces reliable mass exploitation. |
| Impact | This is a genuine but second-tier priority. The supplied CVSS vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.1) describes a network-reachable, unauthenticated flaw (PR:N) in a WordPress theme, which raises its theoretical reach - but the high attack complexity (AC:H) materially tempers that, implying exploitation depends on conditions outside the attacker's direct control rather than being a trivial one-shot request. Only one intelligence source (Patchstack) is present. No EPSS score, no CISA KEV listing, and no public POC are indicated in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the risk signal rests entirely on the vendor-assigned CVSS. The I:H/A:H ratings are also questionable for a vulnerability titled 'Local File Inclusion' (CWE-98): LFI is primarily a confidentiality issue, and integrity/availability impact would only materialize if the inclusion can be escalated to code execution (e.g., log poisoning or inclusion of attacker-controlled uploads) - this is plausible for CWE-98 but is not stated in the description, so treat I:H/A:H as unverified. Net: a real vulnerability worth patching, but the AC:H gating plus absence of EPSS/KEV/POC signals suggests it is not a mass-exploitation emergency. |
| Exploit ScenarioDerived | A remote attacker sends a crafted request to a vulnerable parameter in a site running the Biolife theme (<= 3.2.3), causing the PHP application to include a local file path chosen by the attacker and return its contents (e.g., wp-config.php or other sensitive files). No authentication is required (PR:N), but the high attack complexity means success likely depends on specific conditions such as particular encoding, configuration, or a reachable file path. No public exploit code is identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 10, 2026
Unauthenticated local file inclusion in the KuteThemes Biolife WordPress theme through version 3.2.3 allows remote attackers to steer a PHP include/require path and read arbitrary files from the hosting server, exposing wp-config.php database credentials, API keys, and other sensitive content. The reported vector scores 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), but independent assessment narrows realistic impact to confidentiality loss (C:H/I:N/A:N): the attack is unauthenticated and remote, yet high-complexity because the exact vulnerable parameter, encoding, and configuration prerequisites are not documented, so a single guaranteed payload is not established. No public exploit code and no confirmed active exploitation were identified at time of analysis, and exposure is limited to the niche set of sites running this commercial theme at or below 3.2.3.
RemediationAI
No vendor-released patch is identified in the available data at time of analysis, so the exact fixed version cannot be cited and remediation must start with confirming whether KuteThemes has published a release above 3.2.3 - check the theme's update channel and the Patchstack entry at https://patchstack.com/database/wordpress/theme/biolife/vulnerability/wordpress-biolife-theme-3-2-3-local-file-inclusion-vulnerability-2, and if a newer version exists, upgrade to it immediately. If no fixed release is available, the highest-fidelity mitigation is to deactivate and remove the Biolife theme from production sites (its functionality is lost, but the include surface disappears entirely) or to replace it with a maintained theme. Where the theme must stay in place, layer compensating controls with known trade-offs: restrict the PHP process with open_basedir and disable PHP stream wrappers (allow_url_include=Off, and consider filtering php:// and data:// in requests) to blunt traversal and wrapper-based reads, accepting that this can break plugins/theme features that legitimately read files outside the document root; deploy WAF or reverse-proxy rules that reject traversal and wrapper patterns (../, %2e%2e%2f, ..%5c, /etc/passwd, wp-config.php, php://filter) in query strings and POST bodies, accepting some false positives on legitimate file-path input; harden file permissions and move or protect wp-config.php outside the web root, noting WordPress requires it to remain readable by the PHP user so this reduces but does not eliminate exposure; and alert on traversal patterns in access logs for the theme directory to catch probing. None of these substitutes for removing the vulnerable code, and any LFI that reaches wp-config.php should trigger credential rotation for the database and authentication salts plus a full integrity review of the site.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The issue is a PHP local file inclusion in a commercial WordPress theme, tracked as CWE-98 (Improper Control of Filename for Include/Require Statement in a PHP Program). WordPress themes are PHP codebases loaded into every page render of a site using them, and they typically process request data through template files, AJAX handlers, or admin-ajax endpoints; when a value from the request reaches include, require, include_once, or require_once without adequate validation, an attacker can substitute traversal sequences (../, encoded variants, or php://filter wrappers) to make PHP read an unintended file. The affected CPE is cpe:2.3:a:kutethemes:biolife:*:*:*:*:*:*:*:*, matching all Biolife theme releases from the vendor KuteThemes, with the disclosure stating versions up to and including 3.2.3 are vulnerable. Because the network vector is AV:N with PR:N/UI:N, no authentication or user interaction is required, but AC:H in both the vendor and independent vectors reflects that the attacker does not fully control the conditions needed for a successful read - the vulnerable parameter and any required path prefix or wrapper are unconfirmed from the supplied data. The principal read target for an LFI in WordPress is wp-config.php, which yields database credentials and salts and can be a stepping stone to full site compromise; while CWE-98 can in principle escalate to code execution, that outcome is not established by the available evidence, so the assessed impact is confined to information disclosure.
Know when Biolife gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Network, unauthenticated, no UI (AV:N/PR:N/UI:N); AC:H retained per vendor and the gated nature of LFI; impact is file disclosure so C:H with I:N/A:N absent evidence of code execution.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Local File Inclusion in Biolife <= 3.2.3 versions.
Executive ViewAI
Organizations hosting WordPress sites with the KuteThemes Biolife theme version 3.2.3 or earlier are exposed to a high-severity unauthenticated file disclosure issue that could expose database credentials and API keys. No public exploit identified at time of analysis and the attack is complex, but no vendor patch is available, leaving affected sites dependent on mitigations. Leadership should prioritize identifying and isolating any instances of this niche theme to prevent credential compromise and downstream data breaches.
No vendor-released patch identified at time of analysis; interim mitigations include removing or disabling the KuteThemes Biolife theme at version 3.2.3 or earlier, using WAF virtual patching to block local file inclusion attempts, restricting wp-config.php file permissions, and monitoring logs for unauthorized file access.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Local File Inclusion vulnerabilities occur when an application accepts user-controlled input to specify which file should be loaded or executed, typically through functions like PHP's `include()`, `require()`, or `fopen()`.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Local file inclusion vulnerability in kutethemes Biolife WordPress theme versions up to 3.2.3 enables authenticated atta
Reflected cross-site scripting in the Biolife WordPress theme (versions up to and including 3.2.3) allows an unauthentic
Incorrectly configured access control in kutethemes Biolife WordPress theme version 3.2.3 and earlier allows unauthentic
EUVD-2026-96499
GHSA-hfhp-gvc8-6hcg
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB