CVE-2026-7798

MEDIUMNVD 5.45.4—
EchelonGraph scoreMEDIUM confidence

Score 5.4 from GitHub Security Advisory published 2026-05-22. NVD baseline CVSS 5.4; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
5.4EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 1%CVSS: 5.4Exploit: Elevated riskExposed: 0

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

The FluentCRM – Email Newsletter, Automation, Email Marketing, Email Campaigns, Optins, Leads, and CRM Solution plugin for WordPress is vulnerable to Blind Server-Side Request Forgery in all versions up to, and including, 2.9.87 via the 'SubscribeURL' parameter. This makes it possible for unauthenticated attackers to make web requests to arbitrary locations originating from the web application and can be used to query and modify information from internal services. Exploitation requires that the SES bounce handling key ('_fc_bounce_key') has never been stored (i.e., the site is in its default/unconfigured state with respect to SES bounce handling) as visiting the bounce configuration page auto-generates and stores a random key that causes the authentication check to evaluate correctly and reject unauthenticated requests.

CVSS v3
5.4
EG Score
5.4(medium)
EG Risk
40(Track)
EG Risk 40/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
Severity54% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
1%
EPSS %ILE
52%
KEV
Not listed

Published

May 22, 2026

Last Modified

July 23, 2026

References (8)

Vendor Advisories for CVE-2026-7798(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 6× in last 7d / 26× 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.

Showing the most recent 100 of 190 total refreshes for this CVE.

  1. 2026-09-20 20:16 UTCEPSS rescore
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-16 14:08 UTCEPSS rescore
  4. 2026-09-16 05:15 UTCEPSS rescore
  5. 2026-09-15 03:12 UTCEPSS rescore
  6. 2026-09-15 03:12 UTCEPSS rescore
  7. 2026-09-11 14:53 UTCEPSS rescore
  8. 2026-09-11 14:53 UTCEPSS rescore
  9. 2026-09-08 22:01 UTCEPSS rescore
  10. 2026-09-06 13:48 UTCEPSS rescore
  11. 2026-09-04 05:07 UTCEPSS rescore
  12. 2026-09-02 14:12 UTCEPSS rescore
  13. 2026-09-01 13:54 UTCEPSS rescore
  14. 2026-09-01 04:40 UTCEPSS rescore
  15. 2026-09-01 04:40 UTCEPSS rescore
  16. 2026-08-30 19:18 UTCEPSS rescore
  17. 2026-08-30 19:17 UTCEPSS rescore
  18. 2026-08-30 01:22 UTCEPSS rescore
  19. 2026-08-28 21:42 UTCEPSS rescore
  20. 2026-08-27 14:25 UTCEPSS rescore
  21. 2026-08-26 14:47 UTCEPSS rescore
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-24 14:18 UTCEPSS rescore
  24. 2026-08-23 16:42 UTCEG score recompute
  25. 2026-08-23 16:42 UTCGHSA enrichment
Show 75 more
  1. 2026-08-23 00:19 UTCEPSS rescore
  2. 2026-08-21 23:49 UTCEPSS rescore
  3. 2026-08-21 21:41 UTCEG score recompute
  4. 2026-08-21 21:41 UTCGHSA enrichment
  5. 2026-08-20 22:56 UTCEPSS rescore
  6. 2026-08-20 18:40 UTCEG score recompute
  7. 2026-08-20 18:40 UTCGHSA enrichment
  8. 2026-08-19 17:04 UTCEPSS rescore
  9. 2026-08-18 13:49 UTCEPSS rescore
  10. 2026-08-18 13:49 UTCEPSS rescore
  11. 2026-08-17 13:47 UTCEPSS rescore
  12. 2026-08-17 09:44 UTCEG score recompute
  13. 2026-08-17 09:44 UTCGHSA enrichment
  14. 2026-08-16 14:56 UTCEPSS rescore
  15. 2026-08-16 14:56 UTCEPSS rescore
  16. 2026-08-16 03:20 UTCEG score recompute
  17. 2026-08-16 03:20 UTCGHSA enrichment
  18. 2026-08-16 02:15 UTCEPSS rescore
  19. 2026-08-15 01:53 UTCEG score recompute
  20. 2026-08-15 01:53 UTCGHSA enrichment
  21. 2026-08-15 01:31 UTCEPSS rescore
  22. 2026-08-14 01:53 UTCEG score recompute
  23. 2026-08-14 01:53 UTCGHSA enrichment
  24. 2026-08-13 22:00 UTCEPSS rescore
  25. 2026-08-13 01:23 UTCEG score recompute
  26. 2026-08-13 01:23 UTCGHSA enrichment
  27. 2026-08-12 13:51 UTCEPSS rescore
  28. 2026-08-12 01:23 UTCEG score recompute
  29. 2026-08-12 01:23 UTCGHSA enrichment
  30. 2026-08-11 13:43 UTCEPSS rescore
  31. 2026-08-11 01:23 UTCEG score recompute
  32. 2026-08-11 01:23 UTCGHSA enrichment
  33. 2026-08-11 00:00 UTCEPSS rescore
  34. 2026-08-10 01:24 UTCEG score recompute
  35. 2026-08-10 01:24 UTCGHSA enrichment
  36. 2026-08-09 13:47 UTCEPSS rescore
  37. 2026-08-09 01:24 UTCEG score recompute
  38. 2026-08-09 01:24 UTCGHSA enrichment
  39. 2026-08-08 16:37 UTCEPSS rescore
  40. 2026-08-07 21:11 UTCEG score recompute
  41. 2026-08-07 21:11 UTCGHSA enrichment
  42. 2026-08-06 21:11 UTCEG score recompute
  43. 2026-08-06 21:11 UTCGHSA enrichment
  44. 2026-08-06 13:47 UTCEPSS rescore
  45. 2026-08-05 21:11 UTCEG score recompute
  46. 2026-08-05 21:11 UTCGHSA enrichment
  47. 2026-08-05 19:17 UTCEPSS rescore
  48. 2026-08-05 19:17 UTCEPSS rescore
  49. 2026-08-04 15:10 UTCEPSS rescore
  50. 2026-08-04 10:39 UTCEPSS rescore
  51. 2026-08-03 18:46 UTCEG score recompute
  52. 2026-08-03 18:46 UTCGHSA enrichment
  53. 2026-08-03 10:36 UTCEPSS rescore
  54. 2026-08-02 17:18 UTCEG score recompute
  55. 2026-08-02 17:18 UTCGHSA enrichment
  56. 2026-08-02 02:27 UTCEPSS rescore
  57. 2026-08-01 17:18 UTCEG score recompute
  58. 2026-08-01 17:18 UTCGHSA enrichment
  59. 2026-08-01 04:16 UTCEPSS rescore
  60. 2026-07-30 16:28 UTCEPSS rescore
  61. 2026-07-30 01:30 UTCEPSS rescore
  62. 2026-07-29 17:33 UTCEG score recompute
  63. 2026-07-29 17:33 UTCGHSA enrichment
  64. 2026-07-28 15:37 UTCEPSS rescore
  65. 2026-07-27 14:14 UTCEPSS rescore
  66. 2026-07-26 14:54 UTCEPSS rescore
  67. 2026-07-26 08:07 UTCEG score recompute
  68. 2026-07-26 08:07 UTCGHSA enrichment
  69. 2026-07-25 14:18 UTCEPSS rescore
  70. 2026-07-24 14:18 UTCEPSS rescore
  71. 2026-07-23 14:18 UTCEPSS rescore
  72. 2026-07-23 03:23 UTCEG score recompute
  73. 2026-07-22 14:08 UTCEPSS rescore
  74. 2026-07-22 14:08 UTCEPSS rescore
  75. 2026-07-21 15:25 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2026/CVE-2026-7798.yaml
    First seen Jan 1, 2026

    WordPress FluentCRM <= 2.9.87 - Unauthenticated Blind SSRF

    Open source ↗

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-7798?
CVE-2026-7798 is a medium vulnerability published on May 22, 2026. The FluentCRM – Email Newsletter, Automation, Email Marketing, Email Campaigns, Optins, Leads, and CRM Solution plugin for WordPress is vulnerable to Blind Server-Side Request Forgery in all versions up to, and including, 2.9.87 via the 'SubscribeURL' parameter. This makes it possible for…
When was CVE-2026-7798 disclosed?
CVE-2026-7798 was first published in the National Vulnerability Database on May 22, 2026, with the most recent update on July 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7798 actively exploited?
CVE-2026-7798 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 1% probability of exploitation in the next 30 days, which ranks it in the top 48.5% of all scored CVEs.
What is the CVSS score of CVE-2026-7798?
CVE-2026-7798 has a CVSS v3 base score of 5.4 (NVD).
How do I remediate CVE-2026-7798?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7798, 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-7798

Explore →

Is Your Infrastructure Affected by CVE-2026-7798?

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

Start Free Scan →Browse All CVEs