Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSend crafted HTTP request to theme endpoint
-
ExploitInject traversal path into include parameter
-
ExecutionServer includes targeted local file
-
ImpactDisclose sensitive file contents (e.g., credentials)
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 reaching the Flipmart theme's vulnerable file-inclusion code path with attacker-controlled input that is passed into a PHP include/require (CWE-98), on a WordPress site running the Flipmart theme at version 2.8 or earlier. No authentication is required (PR:N) and no user interaction is needed (UI:N), but the CVSS AC:H rating indicates meaningful limiting factors - exploitation likely depends on specific request parameters, path-traversal or stream-wrapper encoding, or particular PHP/server configuration (e.g., allow_url_include, readable target files) rather than succeeding against every deployment on a first attempt. Escalation beyond file disclosure to code execution depends on the presence of includable attacker-influenced content (logs, uploads, wrappers). The exact vulnerable parameter/endpoint is not specified in the available data. |
| Impact | This is a serious but not top-tier-emergency issue. The provided CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H, base 8.1 High) shows a network-reachable, unauthenticated flaw (PR:N) requiring no user interaction, which raises its priority. The mitigating signal is AC:H - high attack complexity - indicating exploitation is not fully trivial and likely depends on specific conditions, encoding, or timing. No EPSS probability, no CISA KEV listing, and no public POC are present in the supplied data, so there is no public exploit identified at time of analysis and no evidence of active exploitation; the AC:H rating alone lowers the odds of mass, commoditized scanning versus a PR:N/AC:L bug. Note a signal tension worth verifying: the input vector asserts full C:H/I:H/A:H, but the vulnerability is described as 'Local File Inclusion' and tagged 'Information Disclosure,' which typically maps to a confidentiality-dominant impact - the claimed integrity/availability impact likely reflects CWE-98's potential to escalate LFI into code execution (e.g., log/wrapper/uploaded-file inclusion) rather than confirmed I/A loss; confirm the real impact ceiling with Patchstack. Net: a real patch-worthy priority for any site running the Flipmart theme, but the absence of KEV/EPSS/POC and the AC:H gate argue against treating it as an immediate wormable emergency. |
| Exploit ScenarioDerived | A remote attacker, without any credentials, sends a crafted HTTP request to a vulnerable Flipmart theme endpoint that passes attacker-controlled input into a PHP file-inclusion call, causing the server to read and return a sensitive local file (such as wp-config.php) or, if conditions allow inclusion of attacker-influenced content, to execute PHP. The AC:H rating means the request likely needs specific parameters, path traversal/encoding, or a particular configuration to succeed. 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 Flipmart WordPress theme (versions up to and including 2.8, published by ckthemes) allows remote attackers to force the theme's PHP code to include and disclose files on the underlying server. The CVSS vector (CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N per this assessment) confirms no authentication (PR:N) and no user interaction (UI:N) are needed, but the high attack-complexity rating indicates exploitation depends on specific request parameters, path-traversal or stream-wrapper encoding, or particular PHP/server configuration rather than succeeding against every deployment. The primary demonstrated impact is confidentiality loss (arbitrary file read); escalation to code execution would require includable attacker-influenced content such as logs or uploads and is not established by the available data. No public exploit code and no confirmed active exploitation were identified at time of analysis, and no vendor-released patch has been identified; a Patchstack advisory documents the issue.
RemediationAI
No vendor-released patch identified at time of analysis, so the primary action is to deactivate and remove the Flipmart theme until ckthemes publishes a fixed version; if the theme's design must remain visible, consider a static or cached copy of the front end, accepting that this is a workaround and not a fix. Compensating controls: deploy WAF rules that reject request parameters containing path-traversal sequences (../, %2e%2e%2f, ..%2f) or PHP stream-wrapper schemes (php://filter, php://input, data://, expect://), understanding that obfuscation and alternative encodings may evade signature-based rules; restrict filesystem reach by setting open_basedir to the WordPress installation and disable allow_url_include (and optionally allow_url_fopen) in php.ini, with the trade-off that plugins relying on remote includes or remote fetches may break; and harden file permissions so wp-config.php, .env-style secrets, and backup files are not readable by the web user, noting this reduces but does not eliminate the data exposed via include paths. Because the vulnerable code path executes before/around application logic, log monitoring for repeated traversal or wrapper patterns in query strings is useful as a detection backstop, and any site that cannot immediately remove the theme should treat its configuration secrets as potentially exposed. Monitor the Patchstack advisory (https://patchstack.com/database/wordpress/theme/flipmart/vulnerability/wordpress-flipmart-theme-2-8-local-file-inclusion-vulnerability?_s_id=cve) for an updated fixed version before re-enabling the theme.
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 class is CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program), the classic PHP file-inclusion weakness in which an application passes attacker-influenceable input into an include()/include_once()/require() statement without adequate validation. Flipmart is a commercial WordPress theme from vendor ckthemes, distributed through theme marketplaces and installed as an ordinary wp-content/themes/flipmart directory, so the vulnerable code executes in the web server's PHP process with the web user's filesystem privileges. Because the CPE entry is cpe:2.3:a:ckthemes:flipmart:*:*:*:*:*:*:*:* with no version bound, every release flagged by the advisory through 2.8 is treated as affected. In practice, LFI against a WordPress theme is typically exercised by supplying traversal sequences (../) or PHP stream wrappers such as php://filter/convert.base64-encode/resource=… in the vulnerable parameter, which both bypasses naive string filters and lets an attacker exfiltrate raw PHP source. AC:H reflects that the exact parameter and endpoint are not documented publicly and that success hinges on PHP configuration - for example whether allow_url_include is enabled or whether readable target files exist - and on the attacker's ability to reach the specific code path. Escalation from disclosure to remote code execution is conditional, not automatic: it requires that the included resource be attacker-controllable with PHP parseable content, which is why this assessment scores confidentiality-only impact.
Know when Flipmart 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 and unauthenticated (AV:N/PR:N); AC:H reflects specific conditions for a working include; described as LFI/information disclosure so confidentiality-only (C:H, I/A:N).
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Local File Inclusion in Flipmart <= 2.8 versions.
Executive ViewAI
The Flipmart WordPress theme (versions up to and including 2.8) can allow remote, unauthenticated attackers to read files on affected web servers, potentially exposing configuration files, credentials, or other sensitive data. Because no vendor-released patch identified at time of analysis, any organization hosting sites with this theme should treat it as unsupported risk and prioritize inventory and mitigation. Leadership should care because a successful disclosure could lead to credential compromise, regulatory exposure, and follow-on attacks, even though no public exploit identified at time of analysis and exploitation depends on specific conditions.
Deactivate or remove the Flipmart theme (including versions up to and including 2.8) where possible; restrict web-server file permissions and PHP stream wrappers; deploy WAF/virtual patching to block path traversal and local file inclusion attempts; monitor logs for unauthorized file reads; rotate exposed secrets if disclosure is suspected.
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-96485
GHSA-2x8x-ww46-9p6h
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB