Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSend crafted HTTP request to theme endpoint
-
ExploitSatisfy complexity conditions to bypass filtering
-
ExecutionInject path into vulnerable include parameter
-
ImpactDisclose local 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 | Requires a WordPress site with the DukaMarket theme (kutethemes) version 1.3.0 or earlier installed and active, with the vulnerable file-inclusion parameter reachable over the network. Exploitation is unauthenticated (PR:N) and needs no user interaction (UI:N). The High attack complexity (AC:H) is the key limiting factor: successful exploitation depends on conditions not fully under the attacker's control - likely a specific encoding, path-traversal filter bypass, or server/configuration state (e.g., particular PHP settings) - rather than a single trivially repeatable request. Realistic impact is bounded to sites actually running this theme, a relatively small population. |
| Impact | Signals are moderate and partly conflicting. The CVSS 3.1 vector (AV:N/AC:H/PR:N/UI:N) describes a network-reachable, unauthenticated flaw, which raises priority, but the High attack complexity (AC:H) tempers it - successful exploitation depends on conditions outside the attacker's full control rather than being a trivial one-shot request. The 8.1 base score is driven heavily by the input's C:H/I:H/A:H impact triad, yet the vulnerability is described and tagged as 'Information Disclosure' / LFI (CWE-98), which in practice most directly affects confidentiality; the full High integrity and availability impact is not substantiated by the description and should be verified. No EPSS score, no CISA KEV listing, and no public exploit were provided, so there is no public exploit identified at time of analysis. Net assessment: a credible but not emergency-grade issue - unauthenticated and remotely reachable favors patching, while AC:H, limited product footprint, and absence of exploitation evidence argue against treating it as actively weaponized. Note the impact-metric disagreement explicitly: input claims I:H/A:H but an LFI/information-disclosure flaw typically yields confidentiality impact only - verify with Patchstack/vendor before assuming full compromise. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends a crafted HTTP request to a WordPress site running the DukaMarket theme (<=1.3.0), manipulating a parameter that is passed into a PHP include/require path. By satisfying the specific conditions implied by the High attack complexity, the attacker causes the application to load and disclose the contents of local files such as wp-config.php or other sensitive server files. No public exploit code was 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
Local file inclusion in KuteThemes DukaMarket WordPress theme through version 1.3.0 allows a remote unauthenticated attacker to read arbitrary local files on an affected web server, though the independent assessment limits impact to confidentiality only (C:H/I:N/A:N) rather than integrity or availability. Successful exploitation is constrained by high attack complexity (AC:H), typically requiring a specific traversal or filter-bypass condition, and real-world exposure is limited to WordPress sites running this theme. No CISA KEV entry is present, no public exploit identified at time of analysis, and no EPSS score is supplied; the submitted CVSS 8.1 appears to reflect high integrity/availability impact that the independent assessment does not confirm.
RemediationAI
No vendor-released patch identified in the provided data at time of analysis; consult the Patchstack advisory at https://patchstack.com/database/wordpress/theme/dukamarket/vulnerability/wordpress-dukamarket-theme-1-3-0-local-file-inclusion-vulnerability?_s_id=cve for any updated fixed version. Because no exact fix version is supplied, the most reliable mitigation is to deactivate and uninstall the DukaMarket theme and replace it with a maintained theme, accepting the trade-off of a site redesign or loss of theme-specific functionality. If the theme must remain active, deploy WAF rules to block local file inclusion payloads such as directory traversal sequences, php://filter stream wrappers, and known sensitive paths like /etc/passwd, while accepting possible false positives and bypass risk. Harden PHP by setting open_basedir to restrict file access and ensuring allow_url_include is Off and dangerous wrappers are disabled, with the trade-off that legitimate theme features may break. Monitor web server and PHP logs for include/require anomalies and file disclosure attempts.
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
CWE-98 covers improper control of a filename used in PHP include/require statements, often referred to as PHP file inclusion. In DukaMarket versions up to and including 1.3.0, a theme-controlled parameter reaches an include or require construct without adequate sanitization, enabling local file inclusion via directory traversal or PHP stream wrappers. The CPE cpe:2.3:a:kutethemes:dukamarket:*:*:*:*:*:*:*:* identifies the KuteThemes DukaMarket product family, while the advisory scopes the issue to 1.3.0 and earlier. The independently assessed vector AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N indicates the flaw is remotely reachable without authentication or user interaction, but the High attack complexity means exploitation depends on conditions not fully under the attacker's control, such as a specific filter bypass, encoding trick, or PHP/server configuration state. The tags Information Disclosure and LFI support a confidentiality-focused impact rather than code execution in the assessed scope.
Know when Dukamarket 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
Remote unauthenticated LFI yields local file read, so AV:N/PR:N/UI:N and C:H; AC:H reflects the filter/condition dependency; 'Information Disclosure' scope implies no integrity or availability impact.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Local File Inclusion in DukaMarket <= 1.3.0 versions.
Executive ViewAI
KuteThemes DukaMarket, a third-party WordPress theme used on externally facing websites, contains a local file inclusion flaw in versions through 1.3.0 that could let an outside party read files stored on an affected web server. Exposure is limited to organizations that host WordPress sites running this specific theme, and successful exploitation depends on a difficult bypass condition that, as of this analysis, has not been observed in any active campaign. Because no vendor patch is yet available, this should be treated as a contained but time-sensitive risk best addressed through asset inventory and interim mitigations rather than emergency escalation.
No vendor-released patch identified at time of analysis. Interim mitigations: deploy WAF or reverse-proxy virtual patching rules that block path-traversal and local file inclusion patterns against DukaMarket theme paths; deactivate or remove the theme on affected sites; harden web server file permissions and move sensitive files such as wp-config.php outside the readable web root; monitor and alert on file-read attempts targeting theme directories.
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-96458
GHSA-pw5w-c4q7-hmj7
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB