CVE-2026-17018

MEDIUMPre-NVD 4.94.9—
EchelonGraph scoreHIGH confidence

Score 4.9 from GitHub Security Advisory published 2026-08-10. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 4.9; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, epss, ghsa
Trending — 3 sources updated this week
4.9EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.9Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The CubeWP Framework WordPress plugin through 1.1.30 does not perform a per-object read authorization check, nor restrict which metadata keys may be requested, on one of its REST API endpoints, allowing users with the Contributor role and above to read arbitrary post metadata (including that of other users' draft, pending, private, and password-protected posts) and arbitrary user metadata of any user, including administrators.

CVSS v3
4.9
EG Score
4.9(high)
EG Risk
22(Track)
EG Risk 22/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 computed
Severity49% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
13%
KEV
Not listed

Published

August 10, 2026

Last Modified

August 11, 2026

Advisory Details (1)

Auto-updated Aug 11, 2026
🔬 Proof of concept available. No patch confirmed yet.
generic🟡 PoC Available

CubeWP Framework <= 1.1.30 – Contributor+ Arbitrary Post and User Meta Disclosure via IDOR | CVE 2026-17018 | Plugin Vulnerabilities

https://wpscan.com/vulnerability/df87c8d0-b3f3-4995-ac95-d63544e71a32/

Vendor Advisories for CVE-2026-17018(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 20× in last 7d / 32× 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.

  1. 2026-08-20 04:33 UTCEG score recompute
  2. 2026-08-20 04:33 UTCGHSA enrichment
  3. 2026-08-19 17:03 UTCEPSS rescore
  4. 2026-08-19 06:27 UTCGHSA enrichment
  5. 2026-08-18 08:23 UTCEG score recompute
  6. 2026-08-18 08:23 UTCGHSA enrichment
  7. 2026-08-17 13:47 UTCEPSS rescore
  8. 2026-08-17 09:58 UTCEG score recompute
  9. 2026-08-17 09:58 UTCGHSA enrichment
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 11:53 UTCEG score recompute
  12. 2026-08-16 11:53 UTCGHSA enrichment
  13. 2026-08-16 02:14 UTCEPSS rescore
  14. 2026-08-15 13:49 UTCEG score recompute
  15. 2026-08-15 13:49 UTCGHSA enrichment
  16. 2026-08-15 01:30 UTCEPSS rescore
  17. 2026-08-14 15:44 UTCEG score recompute
  18. 2026-08-14 15:44 UTCGHSA enrichment
  19. 2026-08-13 22:00 UTCEPSS rescore
  20. 2026-08-13 17:39 UTCGHSA enrichment
  21. 2026-08-12 19:24 UTCEG score recompute
  22. 2026-08-12 19:24 UTCGHSA enrichment
  23. 2026-08-12 13:50 UTCEPSS rescore
  24. 2026-08-11 21:19 UTCGHSA enrichment
  25. 2026-08-11 20:30 UTCEG score recompute▲ 4.90
Show 7 more
  1. 2026-08-11 20:30 UTCGHSA enrichment
  2. 2026-08-11 20:30 UTCMITRE cvelistV5CVSS v3 → 4.9 · severity → MEDIUM
  3. 2026-08-11 13:42 UTCEPSS rescore
  4. 2026-08-11 00:00 UTCEPSS rescore
  5. 2026-08-10 07:19 UTCNVD update
  6. 2026-08-10 06:41 UTCEG score recompute
  7. 2026-08-10 06:41 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-17018?
CVE-2026-17018 is a medium vulnerability published on August 10, 2026. The CubeWP Framework WordPress plugin through 1.1.30 does not perform a per-object read authorization check, nor restrict which metadata keys may be requested, on one of its REST API endpoints, allowing users with the Contributor role and above to read arbitrary post metadata (including that of…
When was CVE-2026-17018 disclosed?
CVE-2026-17018 was first published in the National Vulnerability Database on August 10, 2026, with the most recent update on August 11, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-17018 actively exploited?
CVE-2026-17018 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 86.9% of all scored CVEs.
What is the CVSS score of CVE-2026-17018?
CVE-2026-17018 has a CVSS v3.1 base score of 4.9 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-17018?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-17018, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-17018

Explore →

Is Your Infrastructure Affected by CVE-2026-17018?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs