CVE-2026-57318

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-06-26. a secondary CVSS source baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
6.5
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 6.5Exploit: NoneExposed: 0

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

Subscriber Sensitive Data Exposure in Site Reviews <= 8.0.11 versions.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
34(Track)
EG Risk 34/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
Severity65% × 45%
Exploitation0% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
28.0%
KEV
Not listed

Published

June 26, 2026

Last Modified

June 26, 2026

Advisory Details (1)

Auto-updated Jun 26, 2026
No patch confirmed yet.
generic

Sensitive Data Exposure in WordPress Site Reviews Plugin - Patchstack

https://patchstack.com/database/wordpress/plugin/site-reviews/vulnerability/wordpress-site-reviews-plugin-8-0-11-sensitive-data-exposure-vulnerability?_s_id=cve

Vendor Advisories for CVE-2026-57318(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 / 61× 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-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:20 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-16 14:09 UTCGHSA enrichment
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 16:57 UTCEPSS rescore
  15. 2026-07-15 15:05 UTCGHSA enrichment
  16. 2026-07-15 02:00 UTCEPSS rescore
  17. 2026-07-15 02:00 UTCEPSS rescore
  18. 2026-07-14 16:20 UTCGHSA enrichment
  19. 2026-07-13 22:31 UTCEPSS rescore
  20. 2026-07-13 17:35 UTCGHSA enrichment
  21. 2026-07-13 06:13 UTCEPSS rescore
  22. 2026-07-13 06:13 UTCEPSS rescore
  23. 2026-07-12 18:50 UTCGHSA enrichment
  24. 2026-07-12 05:46 UTCEPSS rescore
  25. 2026-07-11 20:05 UTCGHSA enrichment
Show 36 more
  1. 2026-07-11 08:27 UTCEPSS rescore
  2. 2026-07-11 08:27 UTCEPSS rescore
  3. 2026-07-10 21:20 UTCGHSA enrichment
  4. 2026-07-09 22:35 UTCGHSA enrichment
  5. 2026-07-09 19:10 UTCEPSS rescore
  6. 2026-07-09 19:10 UTCEPSS rescore
  7. 2026-07-08 23:49 UTCGHSA enrichment
  8. 2026-07-08 15:16 UTCEPSS rescore
  9. 2026-07-08 15:16 UTCEPSS rescore
  10. 2026-07-08 01:04 UTCGHSA enrichment
  11. 2026-07-07 02:19 UTCGHSA enrichment
  12. 2026-07-06 16:27 UTCEPSS rescore
  13. 2026-07-06 16:27 UTCEPSS rescore
  14. 2026-07-06 03:34 UTCGHSA enrichment
  15. 2026-07-06 02:23 UTCEPSS rescore
  16. 2026-07-06 02:23 UTCEPSS rescore
  17. 2026-07-05 04:48 UTCGHSA enrichment
  18. 2026-07-05 02:31 UTCEPSS rescore
  19. 2026-07-05 02:30 UTCEPSS rescore
  20. 2026-07-04 06:31 UTCEPSS rescore
  21. 2026-07-04 06:31 UTCEPSS rescore
  22. 2026-07-04 05:50 UTCGHSA enrichment
  23. 2026-07-03 07:00 UTCGHSA enrichment
  24. 2026-07-02 08:15 UTCGHSA enrichment
  25. 2026-07-01 15:07 UTCEPSS rescore
  26. 2026-07-01 09:28 UTCGHSA enrichment
  27. 2026-06-30 23:22 UTCEPSS rescore
  28. 2026-06-30 10:42 UTCGHSA enrichment
  29. 2026-06-29 14:06 UTCEPSS rescore
  30. 2026-06-29 11:56 UTCGHSA enrichment
  31. 2026-06-28 14:07 UTCEPSS rescore
  32. 2026-06-28 13:10 UTCGHSA enrichment
  33. 2026-06-28 04:56 UTCEPSS rescore
  34. 2026-06-27 14:25 UTCGHSA enrichment
  35. 2026-06-26 15:39 UTCEG score recompute
  36. 2026-06-26 15:39 UTCGHSA enrichment

Frequently asked(5)

What is CVE-2026-57318?
CVE-2026-57318 is a medium vulnerability published on June 26, 2026. Subscriber Sensitive Data Exposure in Site Reviews <= 8.0.11 versions.
When was CVE-2026-57318 disclosed?
CVE-2026-57318 was first published in the National Vulnerability Database on June 26, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-57318 actively exploited?
CVE-2026-57318 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 28.0% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-57318?
CVE-2026-57318 has a CVSS v3 base score of 6.5 (NVD).
How do I remediate CVE-2026-57318?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-57318, 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-57318

Explore →

Is Your Infrastructure Affected by CVE-2026-57318?

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

Start Free Scan →Browse All CVEs