Skip to main content

Verdure Core EUVDEUVD-2026-64789

| CVE-2026-66671 HIGH
PHP Remote File Inclusion (CWE-98)
2026-08-24 Patchstack GHSA-w62x-725c-34v9
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 WordPress site running Verdure Core ≤ 1.2
  2. Delivery
    Send unauthenticated crafted HTTP request
  3. Exploit
    Trigger unsanitized file-path parameter
  4. Execution
    Traverse filesystem via path sequences
  5. Persist
    Include sensitive file (wp-config.php or logs)
  6. Impact
    Extract credentials or execute injected PHP code

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 vulnerability requires no authentication (PR:N confirmed by CVSS vector) and no user interaction (UI:N), but attack complexity is rated High (AC:H), meaning exploitation is not straightforward against arbitrary targets and likely depends on specific server-side conditions such as particular PHP configuration settings, a writable log file accessible via the include path, or a non-default parameter state within the plugin. The Verdure Core plugin version must be 1.2 or earlier and actively installed and enabled on the WordPress site. Exploitation is limited by: (1) AC:H requiring conditions beyond attacker control, likely specific PHP environment settings or plugin configuration state; (2) the scope of readable files being bounded by PHP's open_basedir setting if configured; and (3) escalation to code execution requiring secondary conditions (log poisoning, PHP wrappers) not inherent to the base LFI primitive. Sites with restrictive open_basedir and disabled allow_url_include face materially reduced risk.

Impact

The NVD 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-exploitable flaw with full CIA impact, but the AC:H (High Attack Complexity) metric is the critical moderating factor - exploitation is not trivial and likely requires specific server-side conditions or a multi-step chain. The I:H and A:H ratings appear to presuppose a complete LFI-to-RCE escalation chain rather than the base inclusion primitive; a conservative independent assessment would rate integrity and availability impact lower absent confirmed RCE capability. No EPSS score was provided in the intelligence data; without that signal, exploitation probability must be inferred from the AC:H and the absence of both KEV listing and published POC, suggesting real-world exploitation risk is currently below the CVSS headline would imply. The unauthenticated prerequisite (PR:N) does mean any scanning infrastructure can probe for the flaw at scale. Overall: treat as medium-high operational priority on WordPress sites running this plugin, not an emergency for unaffected deployments.

Exploit ScenarioDerived

An unauthenticated attacker identifies a WordPress site running Verdure Core ≤ 1.2 via passive enumeration (e.g., plugin headers in source) and sends a crafted HTTP GET or POST request with a manipulated file-path parameter targeting a vulnerable inclusion point in the plugin. Under standard attack complexity conditions (AC:H), the attacker must meet a specific server or parameter condition - such as a particular request format or PHP configuration - to trigger successful file inclusion. If successful, the attacker reads wp-config.php to extract database credentials, or poisons an accessible log file with PHP code before including it to achieve remote code execution.

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 – Aug 24, 2026

Local File Inclusion in the Verdure Core WordPress plugin (versions ≤ 1.2) allows unauthenticated remote attackers to include arbitrary files from the server's filesystem by passing unsanitized input to PHP include/require statements. Successful exploitation can expose sensitive server files such as wp-config.php - disclosing database credentials - and, under certain PHP configurations, may enable remote code execution through log poisoning or PHP wrapper abuse. No public exploit code or CISA KEV listing has been identified at time of analysis, though the unauthenticated attack vector lowers the barrier for opportunistic targeting of vulnerable WordPress installations.

RemediationAI

Update the Verdure Core plugin to a version beyond 1.2 once a patched release is confirmed via the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/verdure-core/vulnerability/wordpress-verdure-core-plugin-1-2-local-file-inclusion-vulnerability) and the WordPress plugin repository. No exact patched version number was available in the provided intelligence data, so administrators should verify the current release changelog before updating. If an immediate update is not possible, consider deactivating the Verdure Core plugin until a fix is available, accepting loss of any companion theme functionality it provides. As a server-level compensating control, ensure open_basedir restrictions are configured in php.ini to confine PHP file access to the WordPress installation directory, which limits the files reachable via LFI. Disabling allow_url_include prevents remote file inclusion escalation but does not block local traversal. Web application firewall rules that block path traversal sequences (../) in query parameters and request bodies can reduce opportunistic exploitation risk with minimal application impact.

Affected VersionsENISA

Verdure Core n/a ≤1.2

Affected Packages

euvd verdure_core 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

CWE-98 (Improper Control of Filename for Include/Require Statement in PHP Program) identifies the root cause as insufficient sanitization of user-controlled input before it is passed to PHP's file-inclusion functions. The affected product, identified via CPE cpe:2.3:a:elated-themes:verdure_core:*:*:*:*:*:*:*:*, is a WordPress companion plugin distributed by Elated Themes. In PHP-based WordPress environments, LFI vulnerabilities arise when request parameters directly influence file paths included at runtime, enabling path traversal sequences (e.g., ../../) to target files outside the intended directory. Depending on PHP configuration (allow_url_include, open_basedir, error logging behavior), LFI can escalate to remote code execution through secondary techniques such as log file poisoning, PHP filter wrappers, or session file inclusion.

Know when Verdure Core 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 6.5 MEDIUM

LFI primarily yields confidentiality impact (C:H for file reads); I:L and A:N reflect that RCE escalation is a secondary chain not inherent to the base vulnerability.

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

Executive ViewAI

Why It Matters

Verdure Core WordPress plugin versions 1.2 and earlier contain a local file inclusion vulnerability allowing remote attackers to extract sensitive server files including database credentials from wp-config.php. Under certain PHP configurations, this vulnerability can be leveraged for remote code execution, presenting a complete compromise risk to WordPress sites running the affected plugin.

Business Impact: High
Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations include: (1) disable or remove the plugin immediately; (2) deploy WAF rules to block path traversal patterns against plugin directories; (3) harden PHP configuration with allow_url_include=off and allow_url_fopen=off; (4) establish log monitoring for suspicious file inclusion attempts and wp-config.php access.

Threat Intelligence Overview

EPSS Score
0.3%
Top 80% exploitable
Prevalence
Low
niche WordPress theme companion plugin with limited deployment 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