CVE-2026-78269

MEDIUMPre-NVD 6.46.4—
EchelonGraph scoreHIGH confidence

Score 6.4 from GitHub Security Advisory published 2026-08-24. a secondary CVSS source baseline 6.4; sources differ by 0.0.

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

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

Contributor Server Side Request Forgery (SSRF) in Shared Files <= 1.7.69 versions.

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

Published

August 24, 2026

Last Modified

August 24, 2026

Advisory Details (1)

Auto-updated Aug 24, 2026
No patch confirmed yet.
generic

Server Side Request Forgery (SSRF) in WordPress Shared Files Plugin - Patchstack

https://patchstack.com/database/wordpress/plugin/shared-files/vulnerability/wordpress-shared-files-plugin-1-7-69-server-side-request-forgery-ssrf-vulnerability?_s_id=cve

Vendor Advisories for CVE-2026-78269(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 22× in last 7d / 22× 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-30 01:22 UTCEPSS rescore
  2. 2026-08-29 20:09 UTCEG score recompute
  3. 2026-08-29 20:08 UTCGHSA enrichment
  4. 2026-08-28 21:42 UTCEPSS rescore
  5. 2026-08-28 19:30 UTCGHSA enrichment
  6. 2026-08-27 18:51 UTCEG score recompute
  7. 2026-08-27 18:51 UTCGHSA enrichment
  8. 2026-08-27 14:25 UTCEPSS rescore
  9. 2026-08-26 18:11 UTCEG score recompute
  10. 2026-08-26 18:11 UTCGHSA enrichment
  11. 2026-08-26 14:47 UTCEPSS rescore
  12. 2026-08-25 17:26 UTCEG score recompute
  13. 2026-08-25 17:26 UTCGHSA enrichment
  14. 2026-08-25 13:49 UTCEPSS rescore
  15. 2026-08-24 16:45 UTCGHSA enrichment
  16. 2026-08-24 14:24 UTCEG score recompute
  17. 2026-08-24 14:24 UTCGHSA enrichment
  18. 2026-08-24 13:22 UTCEG score recompute
  19. 2026-08-24 13:22 UTCGHSA enrichment
  20. 2026-08-24 12:21 UTCEG score recompute
  21. 2026-08-24 11:48 UTCEG score recompute
  22. 2026-08-24 11:45 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-78269?
CVE-2026-78269 is a medium vulnerability published on August 24, 2026. Contributor Server Side Request Forgery (SSRF) in Shared Files <= 1.7.69 versions.
When was CVE-2026-78269 disclosed?
CVE-2026-78269 was first published in the National Vulnerability Database on August 24, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-78269 actively exploited?
CVE-2026-78269 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 96.5% of all scored CVEs.
What is the CVSS score of CVE-2026-78269?
CVE-2026-78269 has a CVSS v3 base score of 6.4 (NVD).
How do I remediate CVE-2026-78269?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-78269, 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-78269

Explore →

Is Your Infrastructure Affected by CVE-2026-78269?

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

Start Free Scan →Browse All CVEs