Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessSend crafted HTTP request to theme
-
ExploitInject path into vulnerable PHP include
-
ExecutionApplication reads arbitrary local file
-
ImpactDisclose sensitive file contents (e.g., wp-config.php)
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 | The Uminex WordPress theme (by Kutethemes) version 1.0.9 or earlier must be installed and active on the target site; exploitation is network-based and requires no authentication and no user interaction (PR:N/UI:N), with the attacker supplying attacker-controlled input to a file-inclusion code path (CWE-98). The published vector's AC:H indicates a limiting precondition for reliable exploitation that is not described in the available data - the exact feature, parameter, or configuration that gates the include is undocumented and should be confirmed against the Patchstack advisory. The primary realistic outcome is disclosure of local files (consistent with the 'Information Disclosure'/'LFI' tags); escalation to integrity/availability impact would require further conditions not stated. |
| Impact | Signals are mixed and lean toward moderate real-world priority rather than emergency. The CVSS 3.1 base score of 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H) reflects an unauthenticated, network-reachable flaw with full CIA impact, but the High attack complexity (AC:H) tempers it - the scorer judged that some non-trivial condition must be met for reliable exploitation, which is unusual for a plain LFI and is not explained in the sparse description. No EPSS score, CISA KEV listing, or public POC was provided in the input, so there is no public exploit identified at time of analysis and no evidence of active exploitation. The I:H/A:H ratings in the supplied vector are also in tension with the 'Information Disclosure' and 'LFI' tags, which imply a read-oriented file-disclosure bug; achieving integrity/availability impact (e.g., code execution) from an LFI typically requires additional conditions (log poisoning, session/wrapper tricks) not documented here - verify with the Patchstack advisory. Net: a credible unauthenticated disclosure issue in a WordPress theme worth patching, but the absence of exploitation signals plus AC:H and a niche deployment footprint argue against treating it as an active mass-exploitation threat. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends a crafted HTTP request to a WordPress site running the Uminex theme (<=1.0.9), manipulating a file-path parameter handled by a vulnerable PHP include so the application reads an arbitrary local file (e.g., wp-config.php) and returns its contents. No authentication or user interaction is required (PR:N/UI:N), though the High attack complexity in the published vector suggests some non-default precondition may be needed for reliable exploitation. No public exploit code was identified in the provided data. |
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 Uminex WordPress theme from Kutethemes affects every release up to and including 1.0.9, allowing a remote attacker who can reach an affected installation to supply crafted input to a PHP file-inclusion code path and read files from the underlying server. Patchstack published the issue at CVSS 8.1 (AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H), whereas our independent assessment narrows the realistic outcome to disclosure of local files only (C:H/I:N/A:N) with a lower attack complexity, so integrity and availability impact should not be assumed without a demonstrated exploit. No public exploit code and no CISA KEV entry were identified at time of analysis, and no EPSS score was supplied with the intelligence; the signals are mixed and point to moderate rather than emergency priority.
RemediationAI
No vendor-released patch and no fixed version were identified at time of analysis, and because the advisory covers all releases up to and including 1.0.9, upgrading within the theme is not a confirmed option; the safest action is to deactivate and remove the Uminex theme entirely and migrate to an actively maintained alternative, accepting the loss of the theme's layout and any customizations built on it. If removal is not immediately possible, treat the site as potentially compromised, restrict access to any theme-specific AJAX, admin-ajax, or template endpoints, and apply virtual patching at the WAF or reverse proxy to reject requests whose parameters contain traversal sequences or PHP stream wrappers such as php://filter, php://input, or data://, while recognizing that encoded or double-encoded payloads can bypass naive signatures. Additional compensating controls include blocking direct requests to theme PHP files that are not legitimate front-end entry points, rotating database and secret keys stored in wp-config.php in case file contents have already been exposed, and monitoring for anomalous file-read patterns and outbound traffic from the web server. Confirm exploitation prerequisites and any newly released fix against the Patchstack advisory at https://patchstack.com/database/wordpress/theme/uminex/vulnerability/wordpress-uminex-theme-1-0-9-local-file-inclusion-vulnerability?_s_id=cve, which is currently the only remediation reference available.
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 flaw is a CWE-98 class defect, meaning a PHP program fails to properly control the filename used in an include or require statement. In the Uminex theme this manifests as a local file inclusion vector: attacker-controlled input reaches a file-inclusion sink, and because PHP allows stream wrappers such as php://filter in include paths, an unauthenticated remote request can typically read arbitrary local files (for example wp-config.php with database credentials) by encoding the path through a filter chain. The affected component is the WordPress theme distributed by Kutethemes, identified by the CPE cpe:2.3:a:kutethemes:uminex:*:*:*:*:*:*:*:*, where the wildcard version field combined with the '<= 1.0.9' advisory language indicates that no fixed release has been enumerated and every published version is in scope. The intelligence tags (PHP, WordPress, Theme, LFI, Information Disclosure) align with a classic theme-side include vulnerability. Two discrepancies in the reporting deserve attention: the vendor-published vector scores I:H and A:H, which LFI alone does not normally justify, and its AC:H implies a gating precondition that the available data never names, while our independent assessment treats the vector as AC:L with confidentiality-only impact. The specific feature, shortcode, AJAX action, or query parameter that gates the include remains undocumented and should be confirmed directly against the Patchstack advisory before building detection logic.
Know when Uminex 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 remote LFI with no stated precondition (AV:N/AC:L/PR:N/UI:N); tagged as information disclosure, so C:H with I:N/A:N absent evidence of code execution.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
DescriptionCVE.org
Unauthenticated Local File Inclusion in Uminex <= 1.0.9 versions.
Executive ViewAI
The Uminex WordPress theme from Kutethemes, versions up to and including 1.0.9, contains a high-severity unauthenticated local file inclusion vulnerability (CVE-2026-48193) that could allow attackers to read sensitive files from the web server. Organizations using this theme are at risk of data exposure, including configuration files and credentials, which could lead to further compromise. With no public exploit identified at time of analysis and no vendor-released patch identified at time of analysis, leadership should prioritize immediate mitigating controls and plan for theme replacement.
No vendor-released patch identified at time of analysis. Interim mitigations include deploying WAF rules to block file inclusion attempts, disabling the Uminex theme if not essential, restricting file permissions, monitoring for exploitation attempts, and isolating affected servers.
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-96457
GHSA-3cw5-84p5-rfw8
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB