Skip to main content

KuteShop WordPress Theme CVE-2026-62115

| EUVDEUVD-2026-96503 HIGH
PHP Remote File Inclusion (CWE-98)
2026-10-10 Patchstack GHSA-229w-gqhq-c4fp
8.1
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Identify site using KuteShop theme ≤4.2.9
  2. Delivery
    Send crafted request to vulnerable PHP parameter
  3. Exploit
    Trigger local file inclusion in include path
  4. Execution
    Read sensitive files or execute included code
  5. Impact
    Disclose credentials or gain 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

Exploitation targets the KuteShop WordPress theme at versions 4.2.9 and earlier, requiring that a vulnerable site have this specific commercial theme installed and active; the flaw is reachable without authentication (PR:N) or user interaction (UI:N) over the network (AV:N), so no login or victim action is needed. The limiting factor is the CVSS high attack complexity (AC:H), indicating a specific precondition - likely a particular request format, parameter, or theme configuration/endpoint being accessible - rather than a trivially reproducible default-config exploit; the exact feature or parameter is not named in the available data and must be confirmed against the Patchstack advisory.

Impact

The CVSS 3.1 base score of 8.1 (High) is driven by a network attack vector (AV:N), no privileges (PR:N), and no user interaction (UI:N), combined with high impact to confidentiality, integrity, and availability (C:H/I:H/A:H) - consistent with CWE-98 (improper control of filename for include/require), where a Local File Inclusion can escalate to code execution or broad file disclosure. The one tempering signal is high attack complexity (AC:H), which the vector asserts but the description does not explain; this meaningfully lowers real-world exploitability relative to the headline score. Exploitation status: no public exploit identified at time of analysis - the sole source (Patchstack) reports no POC, and there is no EPSS score or CISA KEV listing provided, so there is no evidence of active or at-scale exploitation. On balance this is a credible but not yet urgent priority: a serious unauthenticated flaw in a specific WordPress commercial theme, but with no exploitation signal and an AC:H qualifier. MISSING DATA: EPSS probability, POC status (beyond Patchstack's silence), and any SSVC decision are absent, and the AC:H rating is unexplained by the description (which reads as a straightforward unauthenticated LFI, more typical of AC:L) - verify the complexity assumption with Patchstack/vendor.

Exploit ScenarioDerived

A remote, unauthenticated attacker sends a crafted request to a KuteShop theme endpoint that passes attacker-influenced input into a PHP include/require path, causing the server to load an arbitrary local file (e.g., wp-config.php) or, via CWE-98 semantics, a controlled payload leading to code execution. No public exploit code is identified at time of analysis, and the CVSS AC:H rating suggests non-trivial preconditions (such as a specific request sequence or encoding) are needed to reliably trigger the inclusion.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 10, 2026

Unauthenticated local file inclusion in the KuteShop WordPress theme through version 4.2.9 allows remote attackers to read files from the hosting server - and, given the CWE-98 root cause, potentially to influence which PHP file is included - without any login or victim interaction. The issue is rated CVSS 3.1 8.1 (High) with a network vector (AV:N), no privileges (PR:N) and no user interaction (UI:N), but high attack complexity (AC:H), which indicates exploitation depends on a specific request format, parameter, or theme configuration rather than a trivial default-configuration request. Impact is high across confidentiality, integrity, and availability; no public exploit identified at time of analysis, and reports come from Patchstack, so exposure is limited to sites running this commercial theme with an affected version installed and active.

RemediationAI

Patch status is not confirmed in the available data: no vendor-released fix version is stated, so treat the Patchstack advisory (https://patchstack.com/database/wordpress/theme/kuteshop/vulnerability/wordpress-kuteshop-theme-4-2-9-local-file-inclusion-vulnerability-2) as the authoritative source for the corrected release and apply the latest KuteShop theme version from KuteThemes as soon as it is published; because this is a commercial theme, verify the fixed version against the vendor changelog rather than assuming the current download is patched. If the theme is not required, deactivate and delete it - the strongest control, with the trade-off of losing the site's design. While awaiting a fix, deploy WAF or reverse-proxy rules that reject path-traversal and stream-wrapper patterns (../, ..%2f, php://filter, php://input, data://, and requests referencing /etc/passwd or wp-config.php) in query strings and POST bodies, accepting that encoded variants can bypass weak rules and that broad rules risk false positives on legitimate traffic. Set open_basedir in php.ini to restrict PHP file access to the web root and uploads directory, and tighten filesystem permissions so wp-config.php is readable only by its owner account; both limit what an LFI can reach but may break plugins or scripts that legitimately read files outside those paths. Add application-level logging and alerting on traversal-style requests and unexpected inclusion of non-theme files, and consider disabling any unused theme AJAX/REST handlers once the vulnerable parameter is identified. These are temporary compensating controls, not substitutes for upgrading.

Affected VersionsENISA

KuteShop n/a ≤4.2.9

Affected Packages

euvd kuteshop no fix

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 affected component is the KuteShop commercial WordPress theme distributed by KuteThemes (CPE cpe:2.3:a:kutethemes:kuteshop:*:*:*:*:*:*:*:*), a PHP application layer that runs inside WordPress. The vulnerability class is CWE-98, improper control of filename for include/require statements, the classic PHP file-inclusion weakness where a script passes an externally supplied value into include(), include_once(), require(), or require_once() without validating it against an allowlist or stripping path-traversal and stream-wrapper syntax. Because WordPress themes are ordinary PHP executing with the web server's privileges, a successful inclusion can disclose sensitive files (wp-config.php and its database credentials, .env files, system files via ../../ traversal or php://filter wrappers) and, where an attacker can place content in an includable file (uploads, logs, session files), can be chained toward code execution - which explains the C:H/I:H/A:H scoring. The unauthenticated, no-interaction characteristics (PR:N/UI:N) mean the vulnerable code path is reachable from an anonymous HTTP request, while the AC:H metric signals a precondition in the request or configuration that the available data does not name; the exact endpoint and parameter must be confirmed from the Patchstack advisory before building detections.

Know when Kuteshop 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

Vendor (Patchstack) PRIMARY 8.1 HIGH
AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 8.1 HIGH

Unauthenticated network-reachable LFI (AV:N/PR:N/UI:N); CWE-98 inclusion can yield file disclosure and code execution (C/I/A:H); AC:H retained from input absent evidence to lower it.

3.1 AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
4.0 AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector
Network
Attack Complexity
High
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

DescriptionCVE.org

Unauthenticated Local File Inclusion in KuteShop <= 4.2.9 versions.

Executive ViewAI

Why It Matters

A high-severity unauthenticated file inclusion flaw affects the KuteShop commercial WordPress theme in all versions through 4.2.9, allowing an outside attacker with no credentials or user interaction to read files from the web server hosting any site where the theme is installed and active, with the potential to influence which PHP file is executed. Because no vendor patch is currently available, every storefront, marketing site, or campaign page running this theme remains exposed, and the affected systems typically house customer records, order data, configuration files, and credentials that carry direct regulatory and reputational consequences if disclosed.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or remove the KuteShop theme where operationally feasible; if it must remain active, front the site with a WAF or reverse proxy enforcing path traversal and parameter allowlisting, block direct HTTP access to wp-config.php and other sensitive files, apply least-privilege file permissions on the web root, disable in-dashboard PHP/plugin/theme file editing, and enable file-integrity monitoring and access logging to detect unauthorized file inclusion attempts.

Threat Intelligence Overview

EPSS Score
0.3%
Top 81% exploitable
Prevalence
Low
niche commercial WordPress WooCommerce theme, limited production footprint
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

40
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +40
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy