CVE-2026-11370

MEDIUMPre-NVD 6.46.4—
EchelonGraph scoreMEDIUM confidence

Score 6.4 from GitHub Security Advisory published 2026-06-24. 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.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.

The WP Meta SEO plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 4.5.18 via the 'new_link' parameter. This makes it possible for authenticated attackers, with contributor-level access and above, to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. The HTTP response status from outbound requests is reflected back in the AJAX JSON response as status_code, providing an enumeration oracle usable for probing internal hosts and cloud metadata services.

CVSS v3
6.4
EG Score
6.4(medium)
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
15%
KEV
Not listed

Published

June 24, 2026

Last Modified

June 29, 2026

References (4)

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

Frequently asked(5)

What is CVE-2026-11370?
CVE-2026-11370 is a medium vulnerability published on June 24, 2026. The WP Meta SEO plugin for WordPress is vulnerable to Server-Side Request Forgery in all versions up to, and including, 4.5.18 via the 'newlink' parameter. This makes it possible for authenticated attackers, with contributor-level access and above, to make web requests to arbitrary locations…
When was CVE-2026-11370 disclosed?
CVE-2026-11370 was first published in the National Vulnerability Database on June 24, 2026, with the most recent update on June 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-11370 actively exploited?
CVE-2026-11370 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 85.3% of all scored CVEs.
What is the CVSS score of CVE-2026-11370?
CVE-2026-11370 has a CVSS v3 base score of 6.4 (NVD).
How do I remediate CVE-2026-11370?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-11370, 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-11370

Explore →

Is Your Infrastructure Affected by CVE-2026-11370?

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

Start Free Scan →Browse All CVEs