The ECS WordPress plugin before 4.3.8 does not have capability or ownership checks on its dynamic repeater actions, relying only on a nonce available to any user who can open the page builder, allowing users with a contributor-level account or above to read, alter and delete the binding configuration of posts they do not own and to change the ECS WordPress plugin before 4.3.8's site-wide presets.
CVE-2026-18807
Score 4.3 from GitHub Security Advisory published 2026-08-15. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 4.3; sources differ by 0.0.
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(high)
- EG Risk
- 35(Track)EG Risk 35/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 computedSeverity43% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- 0%
- EPSS %ILE
- 5%
- KEV
- Not listed
Published
August 15, 2026
Last Modified
August 17, 2026
Advisory Details (1)
Auto-updated Aug 17, 2026ECS < 4.3.8 – Contributor+ Arbitrary Post Binding and Global Preset Modification via Dynamic Repeater Handlers | CVE 2026-18807 | Plugin Vulnerabilities
https://wpscan.com/vulnerability/bf500bf2-1684-4ca1-a8ad-bcff9cbc127c/Vendor Advisories for CVE-2026-18807(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 17× in last 7d / 17× 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-19 20:29 UTCEG score recompute
- 2026-08-19 20:29 UTCGHSA enrichment
- 2026-08-19 17:03 UTCEPSS rescore
- 2026-08-18 21:01 UTCEG score recompute
- 2026-08-18 21:01 UTCGHSA enrichment
- 2026-08-18 13:48 UTCEPSS rescore
- 2026-08-17 21:34 UTCEG score recompute
- 2026-08-17 21:34 UTCGHSA enrichment
- 2026-08-17 20:45 UTCEG score recompute▲ 4.30
- 2026-08-17 20:45 UTCGHSA enrichment
- 2026-08-17 20:44 UTCMITRE cvelistV5CVSS v3 → 4.3 · severity → MEDIUM
- 2026-08-17 13:47 UTCEPSS rescore
- 2026-08-16 14:56 UTCEPSS rescore
- 2026-08-16 02:14 UTCEPSS rescore
- 2026-08-15 06:20 UTCNVD update
- 2026-08-15 06:13 UTCEG score recompute
- 2026-08-15 06:12 UTCMITRE cvelistV5first tracked
Related CVEs(same CWE)
Same CWE
10 shownCWE-862
- CVE-2013-3960EG 9.9CRITICAL
- CVE-2015-10143EG 9.8CRITICAL
- CVE-2016-11036EG 9.8CRITICAL
- CVE-2018-11541EG 9.8CRITICAL
- CVE-2011-4183NVD 6.5EG 9.8CRITICAL
- CVE-2018-10251EG 9.8EPSS p91CRITICAL
- CVE-2018-1217EG 9.8EPSS p99CRITICAL
- CVE-2018-0015EG 9.8CRITICAL
- CVE-2017-12582EG 9.8CRITICAL
- CVE-2017-1000056EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-18807?
When was CVE-2026-18807 disclosed?
Is CVE-2026-18807 actively exploited?
What is the CVSS score of CVE-2026-18807?
How do I remediate CVE-2026-18807?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-18807
Is Your Infrastructure Affected by CVE-2026-18807?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.