Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-78562 – Unauthenticated Local File Inclusion – Verdure Core WordPress Plugin (≤ 1.2)

Be the first to know when new zero-days emerge:

Summary

CVE-2026-78562 is a Local File Inclusion (LFI) vulnerability in the Verdure Core WordPress plugin (developed by Mikado-Themes), affecting all versions up to and including 1.2. The flaw allows unauthenticated, remote attackers to include and execute arbitrary files on the web server, potentially leading to full remote code execution. The vulnerability has a CVSS v3.1 base score of 8.1 (High).

Technical details

  • Root cause: The plugin fails to properly sanitize or restrict a user-supplied filename parameter that is passed into a PHP include/require statement (CWE-98: Improper Control of Filename for Include/Require Statement in PHP Program).
  • Trigger conditions: No authentication is required to exploit the vulnerability; an attacker only needs network access to a vulnerable WordPress site running the affected plugin.
  • Attack vector: Network-based (AV:N), with high attack complexity (AC:H), no privileges required (PR:N), and no user interaction required (UI:N).
  • Impact: Successful exploitation allows attackers to include and execute arbitrary PHP files on the server. This can be leveraged to bypass access controls, disclose sensitive data, or achieve remote code execution — particularly in environments where "safe" file types such as images can be uploaded and subsequently included by the vulnerable code path. The CVSS impact metrics (C:H/I:H/A:H) reflect complete loss of confidentiality, integrity, and availability.

Affected software

  • Product: Verdure Core (WordPress plugin)
  • Vendor: Mikado-Themes
  • Affected versions: All versions up to and including 1.2

Severity

  • CVSS v3.1 Base Score: 8.1 (High)
  • Vector String: CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: At the time of publication, no patched version of Verdure Core has been identified. Security teams should check for and apply any update from Mikado-Themes as soon as it becomes available and monitor the vendor’s release channel for a fixed build beyond 1.2.
  • If no patch is available:
    • Restrict or disable the Verdure Core plugin until a fix is released if the site does not require its functionality.
    • Deploy a Web Application Firewall (WAF) rule to block requests attempting to manipulate file-inclusion parameters (e.g., path traversal sequences such as ../, PHP wrapper prefixes like php://, or unexpected file extensions in relevant request parameters).
    • Audit upload directories and disable execution of PHP within upload/media directories (e.g., via web server configuration) to reduce the impact of file-inclusion attacks that leverage uploaded "safe" file types.
    • Review server and application logs for anomalous requests referencing unexpected file paths or parameters associated with the plugin.
    • Limit exposure of the WordPress admin/plugin infrastructure to trusted networks where feasible until remediation is confirmed.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge