Skip to main content

Armania Theme EUVDEUVD-2026-96495

| CVE-2026-62092 HIGH
PHP Remote File Inclusion (CWE-98)
2026-10-10 Patchstack GHSA-h942-cg9m-fr8x
8.1
CVSS 3.1 · Vendor: Patchstack
View

Attack ChainAIDerived

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

  1. Access
    Reach WordPress site with Armania theme
  2. Delivery
    Send crafted request to inclusion parameter
  3. Exploit
    Trigger local file inclusion (CWE-98)
  4. Execution
    Read wp-config.php / sensitive files
  5. Impact
    Harvest DB credentials and secrets

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 WordPress sites running the Armania theme at version 1.4.8 or earlier; the attacker reaches a theme code path that passes attacker-influenced input into a PHP include/require (CWE-98) with no authentication (PR:N) and no user interaction (UI:N). The limiting factor is the vendor's AC:H rating: a non-trivial precondition must be satisfied for reliable exploitation (the exact required parameter, path format, or configuration is not detailed in the available data and should be verified against the Patchstack advisory). The site must actually have the Armania theme installed and active, which bounds the exposed population.

Impact

The vendor (Patchstack) CVSS 3.1 vector CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H (base 8.1) describes a network-reachable, unauthenticated (PR:N) flaw requiring no user interaction but with high attack complexity (AC:H), yielding high confidentiality, integrity, and availability impact. The high complexity rating is the key tempering signal: it implies the attacker must satisfy some non-trivial precondition (e.g. a specific request/path structure or race), which lowers real-world exploitability relative to the raw 8.1 score. No EPSS score, no CISA KEV listing, and no public POC were supplied in the input, so exploitation status is 'no public exploit identified at time of analysis' - there is no evidence of active or at-scale exploitation. CWE-98 (improper control of filename for include/require in PHP) and the 'LFI'/'Information Disclosure' tags indicate the primary demonstrated impact is arbitrary local file reads; the vendor's I:H/A:H ratings suggest they judge the file inclusion can be escalated to code execution (e.g. via PHP wrappers or log poisoning), but the input does not confirm an RCE technique, so treat I:H/A:H as a vendor assessment rather than independently verified. Net: a genuinely serious unauthenticated flaw in the affected theme, but AC:H plus absence of KEV/POC/EPSS signals place it below drop-everything priority for most environments - patch promptly where Armania is deployed, but it is not evidence of mass exploitation.

Exploit ScenarioDerived

A remote attacker who does not need credentials sends a crafted request to a WordPress site running the Armania theme (<= 1.4.8), manipulating a parameter that controls a PHP include/require path to pull in an attacker-chosen local file. This can disclose sensitive files such as wp-config.php (database credentials, auth keys), and - if the inclusion path can reach attacker-controlled content - potentially escalate to code execution. No public exploit code was identified in the provided data, and the high attack complexity means a non-trivial precondition must be met.

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

Local file inclusion in the Armania WordPress theme (versions up to and including 1.4.8) allows unauthenticated remote attackers to read arbitrary files on the underlying server, potentially exposing sensitive data such as wp-config.php. The vulnerability stems from improper handling of user-supplied input passed to a PHP include/require statement (CWE-98). No public exploit code or active exploitation has been reported at time of analysis; the vendor rates it 8.1 with high attack complexity, while our assessment confirms network reachability with no authentication or user interaction but notes a non-trivial precondition is required for reliable exploitation.

RemediationAI

No vendor-released patch has been identified at time of analysis. Administrators should check the KuteThemes website or the Patchstack advisory for an updated version; if a patched release (e.g., 1.4.9 or later) becomes available, update immediately. If no patch is available, consider deactivating and removing the Armania theme, as it is likely only used for visual presentation and its absence will not affect core functionality (side effect: site appearance changes). As an interim mitigation, deploy a web application firewall (WAF) rule to block path traversal sequences in requests to theme files (e.g., blocking '../' in parameters), though this may cause false positives for legitimate requests. Restrict file permissions to limit the impact of LFI (e.g., ensure wp-config.php is not world-readable). Monitor for indicators of compromise, such as unexpected outbound connections or file reads. Refer to the Patchstack advisory for further guidance: https://patchstack.com/database/wordpress/theme/armania/vulnerability/wordpress-armania-theme-1-4-8-local-file-inclusion-vulnerability?_s_id=cve

Affected VersionsENISA

Armania n/a ≤1.4.8

Affected Packages

euvd armania 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 Armania WordPress theme (CPE: cpe:2.3:a:kutethemes:armania) is a commercial theme from KuteThemes. The vulnerability is a local file inclusion (LFI) caused by improper control of a filename used in a PHP include/require statement (CWE-98). An attacker can supply a crafted path to read arbitrary files on the server, potentially exposing sensitive data like wp-config.php. Our analysis confirms the flaw is network-reachable (AV:N) and requires no authentication (PR:N) or user interaction (UI:N). The vendor rates attack complexity as high (AC:H), indicating a non-trivial precondition must be met for successful exploitation; the exact parameter or path format is not detailed in the available data. While the vendor's CVSS vector lists high confidentiality, integrity, and availability impacts, our independent assessment finds only high confidentiality impact (C:H/I:N/A:N), as the LFI does not inherently allow file modification or code execution.

Know when Armania 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 7.5 HIGH

Unauthenticated remote LFI (AV:N/PR:N); I assess AC:L as LFI typically needs no special conditions, and scope impact to C:H (file disclosure) with I/A:N absent confirmed code-execution, differing from the vendor's AC:H/I:H/A:H.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/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 Armania <= 1.4.8 versions.

Executive ViewAI

Why It Matters

The Armania WordPress theme (versions up to and including 1.4.8) contains a high-severity local file inclusion vulnerability (CVE-2026-62092) that could allow remote attackers to read sensitive files such as wp-config.php, potentially exposing database credentials and leading to full site compromise. No public exploit identified at time of analysis, and no vendor-released patch identified at time of analysis, leaving affected organizations reliant on interim mitigations. Leadership should prioritize identifying and mitigating vulnerable instances to prevent unauthorized access to critical configuration data.

Business Impact: High
Compensating Controls

Temporarily disable the Armania theme; implement WAF rules to block directory traversal; restrict file permissions on wp-config.php; monitor for exploitation attempts.

Threat Intelligence Overview

EPSS Score
0.3%
Top 81% exploitable
Prevalence
Low
niche commercial WordPress theme by kutethemes, limited site 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