The Verdure Core plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 1.2. This makes it possible for unauthenticated attackers to include and execute arbitrary files on the server, allowing the execution of any PHP code in those files. This can be used to bypass access controls, obtain sensitive data, or achieve code execution in cases where images and other “safe” file types can be uploaded and included.
CVE-2026-78562
Score 8.1 from GitHub Security Advisory (severity: HIGH) published 2026-08-25. a secondary CVSS source baseline 8.1; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.1
- EG Score
- 8.1(high)
- EG Risk
- 41(Track)EG Risk 41/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity81% × 45%Exploitation0% × 40%Automatability30% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 39%
- KEV
- Not listed
Published
August 25, 2026
Last Modified
August 26, 2026
Advisory Details (1)
Auto-updated Aug 25, 2026Local File Inclusion in WordPress Verdure Core Plugin - Patchstack
https://patchstack.com/database/wordpress/plugin/verdure-core/vulnerability/wordpress-verdure-core-plugin-1-2-local-file-inclusion-vulnerabilityVendor Advisories for CVE-2026-78562(1)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 10× in last 7d / 10× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-08-26 16:44 UTCEG score recompute
- 2026-08-26 16:44 UTCGHSA enrichment
- 2026-08-26 14:47 UTCEPSS rescore
- 2026-08-26 10:26 UTCGHSA enrichment
- 2026-08-25 21:53 UTCEG score recompute
- 2026-08-25 21:53 UTCGHSA enrichment
- 2026-08-25 13:49 UTCEPSS rescore
- 2026-08-25 09:22 UTCEG score recompute
- 2026-08-25 08:47 UTCEG score recompute
- 2026-08-25 08:46 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-98
- CVE-2012-10025EG 10.0CRITICAL
- CVE-2023-5199NVD 8.8EG 9.9CRITICAL
- CVE-2021-47900EG 9.8CRITICAL
- CVE-2024-13790EG 9.8CRITICAL
- CVE-2024-12571EG 9.8CRITICAL
- CVE-2024-12209EG 9.8EPSS p98CRITICAL
- CVE-2024-10571EG 9.8EPSS p91CRITICAL
- CVE-2024-10871EG 9.8CRITICAL
- CVE-2024-3551EG 9.8CRITICAL
- CVE-2024-33863EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-78562?
When was CVE-2026-78562 disclosed?
Is CVE-2026-78562 actively exploited?
What is the CVSS score of CVE-2026-78562?
How do I remediate CVE-2026-78562?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-78562
Is Your Infrastructure Affected by CVE-2026-78562?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.