Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify WordPress site running ChapterOne ≤1.7
-
DeliverySend crafted request to vulnerable theme endpoint
-
ExploitInject path traversal into include parameter
-
ExecutionPHP includes arbitrary local file
-
PersistExfiltrate wp-config.php or escalate via log poisoning
-
ImpactUse DB credentials or RCE for full site compromise
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 | Exploitation requires that the target WordPress site has the Mikado-Themes ChapterOne theme installed and active at version 1.7 or earlier, and that the attacker can reach the vulnerable theme endpoint over HTTP/HTTPS - typical for any internet-exposed WordPress install. No authentication or user interaction is required (PR:N/UI:N). The AC:H rating indicates a non-trivial attack complexity, meaning the attacker likely needs to know the specific vulnerable parameter name and request shape (not disclosed in the public description), and successful escalation from file disclosure to code execution further depends on PHP configuration (allow_url_include, available log/upload paths writable by the web user) which is not guaranteed in hardened deployments. |
| Impact | The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, 8.1) signals unauthenticated remote reach with high impact across confidentiality, integrity and availability, tempered by high attack complexity - likely reflecting that exploitation depends on specific parameter knowledge or a particular request shape rather than a trivial GET. There is no KEV listing and no EPSS score provided, and Patchstack discloses the issue without bundling a public PoC, so this is currently a theoretical-to-opportunistic risk rather than confirmed active exploitation. Real-world priority is elevated by the unauthenticated nature and by WordPress's tendency to attract mass scanners that quickly weaponize Patchstack disclosures, so defenders running ChapterOne should treat it as high priority even though widespread exploitation is not yet evidenced. |
| Exploit ScenarioDerived | An unauthenticated attacker sends a crafted HTTP request to a ChapterOne theme endpoint (for example an AJAX action or template-loading parameter) supplying a traversal-encoded path that resolves to wp-config.php, retrieving database credentials and WordPress secret keys from the response. With those credentials the attacker can pivot to direct database access or, if log files or uploaded content are includable, escalate the LFI into PHP code execution by including a poisoned log entry or uploaded image containing PHP. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Jun 17, 2026
Unauthenticated local file inclusion in the Mikado-Themes ChapterOne WordPress theme (versions 1.7 and earlier) allows remote attackers to coerce the PHP application into including arbitrary local files via crafted requests. Successful exploitation can disclose sensitive files such as wp-config.php and, depending on server configuration, lead to PHP code execution by including attacker-influenced content. No public exploit identified at time of analysis, but the vulnerability is publicly cataloged by Patchstack.
RemediationAI
No vendor-released patched version is identified in the available data for ChapterOne, so the primary action is to monitor Mikado-Themes and the Patchstack advisory at https://patchstack.com/database/wordpress/theme/chapterone/vulnerability/wordpress-chapterone-theme-1-7-local-file-inclusion-vulnerability for an updated release above 1.7 and apply it immediately when published. In the interim, deploy a WAF rule (Patchstack, Wordfence, or ModSecurity) to block requests containing path traversal sequences (../, encoded variants, php://, file:// wrappers) targeting ChapterOne theme endpoints under /wp-content/themes/chapterone/, with the trade-off of potentially blocking legitimate template parameters; restrict PHP open_basedir to the WordPress root to prevent reading arbitrary system files such as /etc/passwd or /proc, accepting that some plugins relying on system paths may break; and as a last resort switch the site to a different theme until a fix is shipped, recognizing the visual/functional disruption that entails.
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
ChapterOne is a commercial WordPress theme published by Mikado-Themes (CPE cpe:2.3:a:mikado-themes:chapterone). The root cause is CWE-98, improper control of filename for PHP include/require statements, meaning a user-controllable parameter is passed to a PHP file inclusion sink without proper validation, normalization, or allowlisting. In WordPress themes this pattern typically appears in an AJAX action, template loader, or shortcode handler that accepts a path or template name from a request parameter and concatenates it into an include()/require() call, allowing path traversal sequences or absolute paths to reach files outside the intended directory.
Know when Chapterone 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-reachable PHP LFI without auth (AV:N/PR:N/UI:N); AC:H reflects unknown specific parameter/path; primary impact is file disclosure (C:H) with limited integrity and no inherent availability impact absent confirmed RCE chain.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Local File Inclusion in ChapterOne <= 1.7 versions.
Executive ViewAI
The ChapterOne WordPress theme (versions 1.7 and earlier) contains an unauthenticated vulnerability enabling attackers to read arbitrary local files, including wp-config.php with database credentials and encryption keys. Any organization using this theme faces immediate risk of credential theft and site takeover without requiring authentication or user interaction. No public exploit has been identified at time of analysis, but the vulnerability is publicly cataloged and straightforward to weaponize.
No vendor-released patch identified at time of analysis. Interim mitigations: immediately disable or remove the ChapterOne theme; implement file-level access restrictions on wp-config.php via web server or OS-level permissions; deploy WAF rules blocking local file inclusion patterns; enable detailed logging on wp-config.php file access attempts; implement database access monitoring for unauthorized queries; rotate database credentials as precautionary measure; segment network access to database servers to contain potential breach.
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-37596
NVD
CVE.org
EPSS
Vulnrichment
GitHub PoC
Exploit-DB