Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running Kaven theme ≤1.2
-
DeliverySend crafted request to vulnerable include parameter
-
ExploitTrigger local file inclusion in PHP
-
ExecutionRead wp-config.php and sensitive files
-
ImpactHarvest DB credentials / escalate to code execution
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 | Exploitable by unauthenticated remote attackers (PR:N, AV:N, UI:N) against WordPress sites running the CocoBasic Kaven theme version 1.2 or earlier. The CVSS AC:H signals a required non-default precondition or non-deterministic element for reliable exploitation that the public advisory does not fully detail (e.g. a specific theme feature/parameter being reachable, particular PHP configuration such as allow_url_include for any remote inclusion, or knowledge of a valid path); this condition is the primary limiting factor and should be confirmed from the Patchstack advisory. The principal limiter beyond CVSS is deployment scope: Kaven is a niche commercial theme, so the exposed population is small relative to core WordPress or popular plugins. |
| Impact | This is a genuinely serious but not emergency-tier vulnerability. The CVSS 8.1 (HIGH) reflects an unauthenticated (PR:N), network-reachable (AV:N) file-inclusion flaw (CWE-98) with full C:H/I:H/A:H impact, meaning successful exploitation can disclose sensitive files and, given CWE-98's file-inclusion nature, potentially escalate to code execution. However, the attack complexity is explicitly High (AC:H), indicating some non-trivial precondition or non-deterministic element that meaningfully lowers the ease of reliable exploitation - this is the main factor separating it from a trivially mass-exploitable bug. No EPSS score, CISA KEV listing, or public POC is present in the provided data, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The signals are therefore consistent rather than conflicting: high theoretical impact, but AC:H plus a niche WordPress theme footprint point to opportunistic/targeted rather than widespread automated exploitation. Note that CWE-98 formally describes PHP Remote File Inclusion while the description says 'Local File Inclusion' - a minor framing discrepancy worth verifying against the Patchstack advisory for whether remote URL inclusion (and thus RCE) is actually achievable. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a crafted HTTP request to a WordPress site running the Kaven theme (<= 1.2), manipulating a parameter that is passed into a PHP include/require to point at an attacker-chosen file path. This lets them read sensitive files such as wp-config.php (exposing DB credentials and secret keys), and depending on whether remote/wrapper inclusion is possible under CWE-98, potentially achieve code execution. No public exploit code is identified at this time, and the CVSS AC:H indicates a non-trivial precondition must be met for reliable exploitation. |
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 CocoBasic Kaven WordPress theme (versions 1.2 and earlier) allows remote attackers to cause the theme to include and output files from the underlying server, exposing sensitive content such as wp-config.php, credential files, and other data outside the web root. The affected population is limited: Kaven is a niche commercial WordPress theme, so exposure is small compared with core WordPress or high-volume plugins, and no public exploit code has been identified at time of analysis and the flaw is not in CISA KEV. Exploitation is not trivial despite the unauthenticated vector - the CVSS AC:H rating and our independent assessment indicate a required non-default precondition or non-deterministic element (for example a specific theme parameter or feature being reachable, knowledge of an absolute file path, or particular PHP configuration such as allow_url_include) that the public advisory does not fully detail.
RemediationAI
No vendor-released patch version is identified in the available data, so the first step is to consult the Patchstack advisory (https://patchstack.com/database/wordpress/theme/kaven-wp/vulnerability/wordpress-kaven-theme-1-2-local-file-inclusion-vulnerability) to confirm whether an updated Kaven theme release addresses the flaw and, if so, upgrade to that exact version and verify the theme's files were actually replaced rather than only the database record being updated. If no fixed release is available, the most reliable mitigation is to deactivate and remove the Kaven theme from production sites and replace it with a maintained alternative - the trade-off is loss of the theme's specific design and layout, requiring re-theming work, but it eliminates the vulnerable include call entirely. Where removal is not immediately possible, treat the site as potentially compromised-by-read: set PHP open_basedir to confine file access to the web root, ensure allow_url_include is disabled and allow_url_fopen is off (note that disabling these prevents the most severe remote-inclusion escalation but does not stop plain local file reads), and deploy a WAF rule that blocks path-traversal and absolute-path sequences (../, ..%2f, /etc/, php://, data://, file://) targeting theme endpoints - accepting that WAF bypasses are common and this is a compensating control, not a fix. Additionally, rotate database credentials, WordPress salts, and any keys or tokens stored in files readable by the web user if there is any chance the inclusion was exercised, since the High confidentiality impact means those values may already be exposed.
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 root cause is CWE-98, Improper Control of Filename for Include/Require Statement in PHP Program (historically labeled PHP Remote File Inclusion), meaning the theme passes attacker-influenceable input into a PHP include(), include_once(), require(), or require_once() call without adequate validation. Because the vulnerable code lives in a WordPress theme deployed on PHP, a successful inclusion lets the attacker read arbitrary files that the PHP process can access, and where the surrounding configuration permits (for example allow_url_include enabled, or an attacker-writable file that can be included by path), the same primitive can escalate beyond disclosure into code execution - consistent with the assessed CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H vector, whose High integrity and availability impacts indicate the inclusion is not purely a read-only information disclosure in the worst case. The CPE cpe:2.3:a:cocobasic:kaven:*:*:*:*:*:*:*:* confirms the CocoBasic Kaven theme as the affected component, with a wildcard version matching the reported '<= 1.2' range, and all deployments of that theme are potentially in scope. The AC:H qualifier in both the vendor and our independently assessed vector is the key technical nuance: the include is reachable over the network without authentication or user interaction, but reliable exploitation depends on conditions such as reaching the specific vulnerable theme feature, knowing or guessing a valid path, or a non-default PHP setting, which materially narrows practical exploitability.
Know when Kaven 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
Unauthenticated network-reachable file inclusion (PR:N/AV:N/UI:N); AC:H retained for the undisclosed precondition, and CWE-98 file inclusion can lead to code execution justifying C/I/A:H.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Local File Inclusion in Kaven <= 1.2 versions.
Executive ViewAI
The CocoBasic Kaven WordPress theme (versions 1.2 and earlier) carries a high-severity file inclusion flaw, CVE-2026-62067, that could allow an attacker to make a vulnerable site disclose server-side files such as wp-config.php and stored credentials. Because such files typically hold database passwords and authentication salts, a successful attack could enable full site compromise and potential lateral movement into connected systems, although exposure is confined to the limited set of organizations running this niche commercial theme and exploitation requires specific non-default conditions. Leadership should care if any public-facing WordPress property uses Kaven, as no vendor patch is currently available and remediation depends on removing or isolating the theme.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or replace the CocoBasic Kaven theme (versions 1.2 and earlier); take affected sites offline if removal is not feasible; move wp-config.php outside the web root; set allow_url_include=Off and disable remote file inclusion in PHP configuration; restrict file and directory permissions to least privilege; deploy WAF or reverse-proxy virtual patching rules blocking path traversal and file-inclusion requests targeting the theme; and monitor web/PHP logs for exploitation attempts.
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.
EUVD-2026-96482
GHSA-6rcq-7cfg-gp9m
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB