CVE-2026-66619

HIGHPre-NVD 7.67.6—
EchelonGraph scoreHIGH confidence

Score 7.6 from GitHub Security Advisory (severity: HIGH) published 2026-09-17. a secondary CVSS source baseline 7.6; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, secondary
Trending — 3 sources updated this week
7.6EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.6Exploit: None knownExposed: 0

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

Administrator SQL Injection in Newsletters <= 4.18 versions.

CVSS v3
7.6
EG Score
7.6(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
Severity76% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
30%
KEV
Not listed

Published

September 17, 2026

Last Modified

September 19, 2026

Advisory Details (1)

Auto-updated Sep 17, 2026
No patch confirmed yet.
generic

SQL Injection in WordPress Newsletters Plugin - Patchstack

https://patchstack.com/database/wordpress/plugin/newsletters-lite/vulnerability/wordpress-newsletters-plugin-4-18-sql-injection-vulnerability?_s_id=cve

Vendor Advisories for CVE-2026-66619(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 27× in last 7d / 33× 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-09-24 23:00 UTCEG score recompute
  2. 2026-09-24 23:00 UTCGHSA enrichment
  3. 2026-09-24 11:09 UTCGHSA enrichment
  4. 2026-09-23 23:33 UTCEG score recompute
  5. 2026-09-23 23:33 UTCGHSA enrichment
  6. 2026-09-23 17:54 UTCEPSS rescore
  7. 2026-09-23 11:57 UTCGHSA enrichment
  8. 2026-09-23 00:20 UTCEG score recompute
  9. 2026-09-23 00:20 UTCGHSA enrichment
  10. 2026-09-22 12:43 UTCGHSA enrichment
  11. 2026-09-22 01:07 UTCEG score recompute
  12. 2026-09-22 01:07 UTCGHSA enrichment
  13. 2026-09-21 13:31 UTCGHSA enrichment
  14. 2026-09-21 01:55 UTCEG score recompute
  15. 2026-09-21 01:55 UTCGHSA enrichment
  16. 2026-09-20 20:16 UTCEPSS rescore
  17. 2026-09-20 14:18 UTCGHSA enrichment
  18. 2026-09-20 02:42 UTCEG score recompute
  19. 2026-09-20 02:42 UTCGHSA enrichment
  20. 2026-09-19 15:06 UTCGHSA enrichment
  21. 2026-09-19 03:29 UTCEG score recompute
  22. 2026-09-19 03:29 UTCGHSA enrichment
  23. 2026-09-19 02:36 UTCEG score recompute
  24. 2026-09-19 02:36 UTCGHSA enrichment
  25. 2026-09-18 20:37 UTCEG score recompute
Show 8 more
  1. 2026-09-18 20:37 UTCGHSA enrichment
  2. 2026-09-18 19:28 UTCEPSS rescore
  3. 2026-09-18 08:57 UTCGHSA enrichment
  4. 2026-09-17 21:21 UTCEG score recompute
  5. 2026-09-17 21:21 UTCGHSA enrichment
  6. 2026-09-17 14:23 UTCEG score recompute
  7. 2026-09-17 13:34 UTCEG score recompute
  8. 2026-09-17 13:34 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-66619?
CVE-2026-66619 is a high vulnerability published on September 17, 2026. Administrator SQL Injection in Newsletters <= 4.18 versions.
When was CVE-2026-66619 disclosed?
CVE-2026-66619 was first published in the National Vulnerability Database on September 17, 2026, with the most recent update on September 19, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-66619 actively exploited?
CVE-2026-66619 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 70.5% of all scored CVEs.
What is the CVSS score of CVE-2026-66619?
CVE-2026-66619 has a CVSS v3 base score of 7.6 (NVD).
How do I remediate CVE-2026-66619?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-66619, 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-66619

Explore →

Is Your Infrastructure Affected by CVE-2026-66619?

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

Book a Demo →Browse All CVEs