CVE-2026-57681

MEDIUMPre-NVD 6.46.4—
EchelonGraph scoreHIGH confidence

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

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

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

Subscriber Server Side Request Forgery (SSRF) in GeoDirectory <= 2.8.161 versions.

CVSS v3
6.4
EG Score
6.4(high)
EPSS
13.8%
KEV
Not listed

Published

July 2, 2026

Last Modified

July 2, 2026

Advisory Details (1)

Auto-updated Jul 3, 2026
No patch confirmed yet.
generic

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

https://patchstack.com/database/wordpress/plugin/geodirectory/vulnerability/wordpress-geodirectory-plugin-2-8-161-server-side-request-forgery-ssrf-vulnerability?_s_id=cve

Vendor Advisories for CVE-2026-57681(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 / 20× 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-07 07:48 UTCEG score recompute
  2. 2026-07-07 07:48 UTCGHSA enrichment
  3. 2026-07-06 16:27 UTCEPSS rescore
  4. 2026-07-06 16:27 UTCEPSS rescore
  5. 2026-07-06 08:48 UTCEG score recompute
  6. 2026-07-06 08:48 UTCGHSA enrichment
  7. 2026-07-06 02:23 UTCEPSS rescore
  8. 2026-07-06 02:23 UTCEPSS rescore
  9. 2026-07-05 09:49 UTCEG score recompute
  10. 2026-07-05 09:48 UTCGHSA enrichment
  11. 2026-07-05 02:31 UTCEPSS rescore
  12. 2026-07-05 02:30 UTCEPSS rescore
  13. 2026-07-04 10:44 UTCEG score recompute
  14. 2026-07-04 10:44 UTCGHSA enrichment
  15. 2026-07-04 06:31 UTCEPSS rescore
  16. 2026-07-04 06:31 UTCEPSS rescore
  17. 2026-07-03 11:40 UTCEG score recompute
  18. 2026-07-03 11:40 UTCGHSA enrichment
  19. 2026-07-02 12:35 UTCEG score recompute
  20. 2026-07-02 12:35 UTCGHSA enrichment

Related CVEs(same CWE)

Frequently asked(5)

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

Explore →

Is Your Infrastructure Affected by CVE-2026-57681?

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

Start Free Scan →Browse All CVEs